Re: [Bigforth-devel] Turnkey application problems
Brought to you by:
paysan
From: David K. <dvd...@gm...> - 2011-03-27 17:48:34
|
>>>>> "Bernd" == Bernd Paysan <ber...@gm...> writes: > Am Sonntag, 27. März 2011, 13:20:57 schrieb David Kuehling: >> Hi, >> >> I'm just trying to turn the brainless chess playing game [1] into a >> windows turnkey application using bigforth-2.4.0. Stumbled into two >> problems so far: >> >> - Default search path searches bigforth's library directories before >> '.', so it does not load 'environ.fs' which is part of my project but >> is shadowed by a file of the same name in the bigforth library >> directory. > Is this really the case? The default search path starts with ., and > when I put an "environ.fs" into the current directory, it loads from > there. For the linux version you're right. In the windows version, the default setting after installation resulted in Path ";C:\Program Files\bigforth;." > The way to go is to use the module system. [..] Ok, going to give this a try, >> BTW on Linux, bigforth is still about 30% faster than Gforth-64bit >> for the Brainless benchmark. Probably Gforth bloats code too much >> and relies too much on the (too small) BTB. > Both. It's rather the other way round: Being only 30% slower than > bigForth is a huge achievement of Gforth's approach. Well, I think I remember Anton claiming, Gforth were faster in his micro-benchmarks. Just wanted to point out, that Gforth doesn't fare so well under real-world condidtions :) cheers, David -- GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40 |