Hi!
We don't use Sun's implementation of Java, because it's not
ideologically pure ;-) Plus everyone knows that good programming
languages have a specification that doesn't shift like quicksand...
Well, that is partially not true anymore. Sun already released two important
components of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Richard,
On Dec 7, 2006, at 9:35 AM, Richard Lewis wrote:
Hello CHICKEN users,
I'm new both to chicken scheme and, in fact, to scheme itself. I
was attracted
to chicken as soon as I saw that it had a very simple module
management
system.
I think even the most simple kind of Chicken/egg versioning would
go a long way. For example, I can build easyffi and use it in Chicken
2.3 if I simply remove the -G option. So if chicken-setup supported
different build commands for different versions of Chicken, this would
make packaging
Hello Ivan,
On Thu, 07 Dec 2006 13:04:57 -0500 Ivan Raikov [EMAIL PROTECTED] wrote:
I think even the most simple kind of Chicken/egg versioning would
go a long way. For example, I can build easyffi and use it in Chicken
2.3 if I simply remove the -G option. So if chicken-setup supported
Thanks for your replies regarding this.
I've just managed to install easyffi by removing the -G option from
easyffi.setup.
But it looks like I'll have to have a go at self-compilation. Being a Debian
user I'm extremely unused to this sort of thing. Wish me luck ;-)
On Thursday 07 December
Well, I am not the maintainer for the Debian Chicken package, so I
don't know. But unless the more recent versions of Chicken depend on
libraries or library versions that are not present in Debian, it's
probably not that difficult. Actually, the real problem here would be
that the Debian
It seems to me that if Debian provides a Chicken 2.3 package for
stability reasons, then Debian should also provide a 2.3 eggs package
and keep it up to date. Using chicken-setup is inherently unstable
from the perspective of Debian stable, since the eggs are constantly
updated and haven't gone
On Dec 7, 2006, at 11:26 AM, Zbigniew wrote:
It seems to me that if Debian provides a Chicken 2.3 package for
stability reasons, then Debian should also provide a 2.3 eggs package
and keep it up to date. Using chicken-setup is inherently unstable
from the perspective of Debian stable, since
You make a good point; actually, I would say that Debian needs to
have a package for each individual egg, so that the developer who
wishes to release Debian packages of their Chicken code can have
precise control over dependencies. But then this means that the egg
repository must match egg
We don't use Sun's implementation of Java, because it's not
ideologically pure ;-) Plus everyone knows that good programming
languages have a specification that doesn't shift like quicksand...
Kon Lovett [EMAIL PROTECTED] writes:
Thank you. I was just going to mention that. What do
Ivan Raikov scripsit:
We don't use Sun's implementation of Java, because it's not
ideologically pure ;-) Plus everyone knows that good programming
languages have a specification that doesn't shift like quicksand...
Well, Algol (60 and 68) should meet your needs, then, as should PL/I.
11 matches
Mail list logo
