Re: [gforth] Multiple problems with latest Gforth-CVS

[David Kuehling]

>>>>> "Bernd" == Bernd Paysan <address@hidden> writes:

> Am Mittwoch, 28. November 2012, 04:24:38 schrieb David Kuehling:
>> Hi,
>> 
>> after building and installing Gforth from CVS, a few test-cases of a
>> current project don't pass any more.
>> 
>> Here are a few code sequences that don't behave as before:
>> 
>> * gforth -e '1 (bye)'
>> 
>> does not quit any more, it enters the interpreter (doing '0 (bye)'
>> does work however)

> That's because I've prepared Gforth to integrate as library - and it
> now returns via (bye) after startup.  Question: What kind of return
> magic should we use? Maybe something > 255, because 0..255 are values
> useful for exit.

Don't understand exactly what you do, but maybe we should add another
word for returning with an exit code.  (bye) isn't even mentioned
anywehere in the Gforth documentation, I just found it via grep'ing the
sources.  On the other hand, people already may be using (bye), so
changing semantics may be a bad idea.

Gforth as a library... that'll be a nice feature.
[..]
> I'm now mostly working on my new header experiment branch, whihc is a
> git repository here:

> git clone http://bernd-paysan.de/gforth

> I keep merging in changes from CVS, though, and once the experimental
> header stuff is ok with Anton, I'll either check that back into CVS,
> or we move to git officially.

I think it's about time to drop CVS.  It really gets in the way when
working on Gforth sources.  I'm not a big fan of Git, too complex, too
many ways to do the same thing (and even more ways to do it slightly
wrong).  But already much better than CVS.  Does it keep the full
history?  What about moving the Git repo to savannah?

cheers,

David
-- 
GnuPG public key: http://dvdkhlng.users.sourceforge.net/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205  D016 7DEF 5323 C174 7D40

pgpvYeRSmOSid.pgp
Description: PGP signature