[PicForth] PicForth critical bug - broken 'include' mechanism

[David McNab]

Hi,

After a couple of frustrating hours, I've pinpointed a critical bug in 
PicForth (or in PicForth's interaction with gforth), relating to file 
includes.

Simplifying to an example which reproduces the brokenness, I created a 
file called 'junk.fs', which has nested includes as shown below:

junk.fs
   +-junk1.fs
      +-junk1a.fs
          +-junk1b.fs
   +-junk2.fs
      +-junk3.fs

When trying to compile 'junk.fs', gforth has a brain haemorrhage, 
complaining that junk3.fs is a 'nonexistent file'.

The bug manifests when I do:

   gforth picforth.fs -e 'include junk.fs'

It does *not* show when I do:

   gforth -e 'include junk.fs'

I attach a tarball with these demo files.

Any thoughts?

-- 
Cheers
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: broken-picforth.tar.gz
Type: application/x-gzip
Size: 516 bytes
Desc: not available
Url : http://lists.rfc1149.net/pipermail/picforth/attachments/20041103/0fec2ea5/broken-picforth.tar.bin