In that case, perhaps a note about using eggs with different but
compatible licenses should be included in the FAQ, or along with the
main Chicken license. It's just that I had never seen this issue
raised before -- and certainly there are better ways to raise it. Let
us shake hands and move
Licence is not a problem for me yet, because this software
is not for commercial use. I just do not like side effects when
they should not happen, even if they are not crucial at the moment.
The worst thing when they become crucial later.
I don't see the benefit of this standard deviation of
Thanks, Zbigniew. I indeed figured out the renaming of #!rest before
Chicken sees it. But I didn't think of the hack and I'll give it a try
soon. However, it is not a nice solution and my guess would be that the
syntax-case egg should have a build in exception for the #!key and #!rest
keywords, so
Gábor Balázs wrote:
[...]
I don't see the benefit of this standard deviation of chicken scheme.
If one says it is about performance, I can say scheme's text based
read/write is far from the performance what binary I/O can provide.
The real benefit of read/write is simplicity and portability.
On Aug 25, 2007, at 11:16 PM, Ivan Raikov wrote:
nip
Let
us shake hands and move on, indeed -- I am in the process of changing
my unit tests from using the LPGL-ed testeez egg to using the BSD-ed
testbase egg.
While I think the documentation for 'testbase' is comprehensive it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 26, 2007, at 7:16 AM, [EMAIL PROTECTED] wrote:
Thanks, Zbigniew. I indeed figured out the renaming of #!rest before
Chicken sees it. But I didn't think of the hack and I'll give it a try
soon. However, it is not a nice solution and my guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 26, 2007, at 2:42 AM, Gábor Balázs wrote:
Licence is not a problem for me yet, because this software
is not for commercial use. I just do not like side effects when
they should not happen, even if they are not crucial at the moment.
The
Hi there.
There was a change made to the blob-handling code in SVN r5529
(2007-08-19) which caused this error. You cannot build 5529 or later
unless you already have a pretty recent compiler installed for the
bootstrap phase. I don't know exactly how recent yet, but it's
definitely sometime
