gforth
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gforth] Possible oof.fs issue!


From: Bernd Paysan
Subject: Re: [gforth] Possible oof.fs issue!
Date: Mon, 19 Jan 2015 22:31:14 +0100
User-agent: KMail/4.14.3 (Linux/3.16.7-7-desktop; KDE/4.14.3; x86_64; ; )

Am Mittwoch, 24. Dezember 2014, 16:07:31 schrieb Philip Smith:
> Playing around with object stuff and found that oof.fs and oofsampl.fs
> cause the vocs word to work incorretly!
> 
> Following is what i did in version 0.7 gforth:
> 
> require oof.fs
> require oofsampl.fs
> vocs
> 
> Following is what happens after the vocs command is issued:
> :3: Invalid memory address
> :
> >>>vocs<<<
> 
> Backtrace:
> $B6991B80 @
> $B69948A8 >does-code
> $B6991684 interpret/compile?
> $B69916E8 (cfa>int)
> $B69917E8 (x>int)
> $B699BB18 name>int.
> $B69B7EC4
> $B699BC40 .voc
> 
> I have not looked yet at the way oof.fs does objects but i was starting to
> compare mini-oof.fs and objects.fs and oof.fs and found if i make my own
> objects with each of these library's the oof.fs library causes this issue
> with vocs command.  objects.fs and mini-oof.fs do not cause any issues that
> i can see with vocs.

It's an issue of vocs; this is unreliable when displaying wordlists 
(vocabularies without name).  As oof.fs uses these, and the other two don't, 
the issue becomes apparent.

The issue has already been resolved in the current git head version.  As VOCS 
is merely diagnostic, we won't backport the fix.

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://bernd-paysan.de/
net2o ID: kQusJzA;address@hidden(dQ*




reply via email to

[Prev in Thread] Current Thread [Next in Thread]