Re: [Chicken-users] read / write floats

[Gábor Balázs]

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 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.

This latter is lost in our case now. I think read/write is so basic,
the simplest code modules written first for chicken have side
effects or (with using special eggs) become unportable to other
scheme implementations.

My opinion is that any reasonable scheme implementation
should follow the standard first, and extend it second.

`bg`

On 26/08/07, Ivan Raikov <address@hidden> wrote:

  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 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.


    -Ivan


Zbigniew < address@hidden> writes:

> The Chicken core and the vast majority of eggs are BSD or MIT
> licensed; only 43 of 364 eggs are GPL.  It is not unreasonable to
> point this out, in case a new user is unaware that different eggs come
> with a wide variety of licenses (unlike some more homogeneous
> languages).  I did not interpret Kon's remark as attacking the GPL
> license in general nor your choice to use it in particular.  Let us
> shake hands and move on.
>


_______________________________________________
Chicken-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/chicken-users