The csv egg in Chicken 4 has been superseded by tabular in Chicken 5,
which offers a generalized interface for parsing tabular text data,
including fixed-width columns.
-Ivan
On Sat, Sep 28, 2019 at 11:28 AM Matt Welland wrote:
>
> On Sat, 2019-09-28 at 19:18 +0200, Jörg F. Wittenberger wrote:
I think the historical precedent has been to make the big sweeping
change and then frantically rush to fix all broken eggs :-)
But in this case it really sounds like it is better to make all
changes to keyword semantics at once, rather than piecemeal.
-Ivan
On Fri, May 17, 2019 at 12:44 PM
Thanks for making a patch for this issue!
-Ivan
On Thu, Aug 30, 2018 at 4:14 AM wrote:
>
> > > So the basic problem is to install multiple sets of files, in separate
> > > steps? I think for "scheme-include" components this should be possible,
> > > but (as far as I can see) this is not
Yes, exactly, the issue is installing multiple sets of files in
different subdirectories of PREFIX/{include,share}. It would be very
useful for "c-include" as well as "data" components.
Thanks,
-Ivan
On Tue, Aug 28, 2018 at 1:07 PM wrote:
>
> > I have a couple of eggs that generate and compile
Hi Felix,
I think this last question about installing include files is closely
related to my question, so let me try to clarify.
I have a couple of eggs that generate and compile code similar to the
way chicken-crunch works. These eggs would install header or source
files that are required for
t; On Sat, Apr 22, 2017 at 07:17:09AM -0700, Ivan Raikov wrote:
>> It considerably limits the effectiveness of distributing software
>> written in Chicken, because now users who are not familiar with its
>> peculiarities cannot simply run chicken-install. Could at least
I agree that the argvector patch should be merged, as it is a change
that allows Real Work to be done with CHICKEN.
It would be nice to have performance comparisons of course, and I
would be particularly curious to benchmark CPS-style tree traversal
and combinator parsing code. I think having
I think these are lofty goals, but it is way too much work for a single
release.
Perhaps modularising the compiler and refactoring the core modules should
be the goals for 5.0 release,
and points 1.3-1.8 would be done as 5.x releases leading up to 6.0.
As for library names, I favor fully spelled
The Chicken wiki still has an index of Chicken 3 eggs, although I do think
chicken-setup is no longer operational.
Perhaps now would be a good time to clean the wiki of vestigial references
to 2 3.
I also like the idea of adopting the r7rs library names.
-Ivan
On Wed, Aug 20, 2014 at 1:13
I do think it is time for an overhaul, and creating a new major version
branch is the right way to go about it.
Obviously it would take some time to port everything, but it seems that the
changes will be simpler than during the hygienic macros transition.
Ivan
On Aug 19, 2014 12:09 AM, Peter
I would think that support for Chicken 2 3 should be dropped after a
Chicken 5 branch is made.
If anyone desperately needs Chicken 3, would it not be better to migrate
the Chicken 3 stuff to another server?
I had also implicitly assumed that the modularisation changes would help
bring full R7RS
Hi Andy,
The environments egg will not work under Chicken 4.7.4 and later, due to
changes in the internal representation (also noted in the documentation).
The rewrite branch is meant to fix this issue.
Ivan
On Sep 23, 2012 10:09 PM, Andy Bennett andy...@ashurst.eu.org wrote:
Hi,
I
I also do not understand why using different data structures is not
under consideration. There are many algorithms and data structures for
handling collisions so that hash table access remains efficient even with a
high rate of collisions. Why not have the option to choose the data
structure
I think that setting up and maintaining a ratings site might be a bit
too much overhead, and more importantly, it will take effort to
convince people to vote (if the Chicken survey is any indication).
How about we set up a system similar to the Debian popularity contest,
where the Debian
system. Others are also welcome to help.
-Ivan
Ivan Raikov ivan.g.rai...@gmail.com writes:
Ok, I can do some research and see if there is some existing wiki
parser that can be adapted to read the svnwiki dialect and produce
s-expressions. If there are some reasonable solutions out
There are many good reasons not to support R6RS. You might want to read
them here:
http://www.r6rs.org/ratification/results.html
Thomas Bushnell BSG t...@becket.net writes:
So the extraordinary compiler Stalin is sliding into obscurity, because
it remains stuck at r4rs, with nobody having
Chicken Scheme, along with its extension libraries, supports a large
superset of R6RS. Given what you have written below, I do not understand
why you think R6RS should be a guideline for a punchlist of features
to implement in Chicken. It is not a particularly good specification,
and
Ok, I can do some research and see if there is some existing wiki
parser that can be adapted to read the svnwiki dialect and produce
s-expressions. If there are some reasonable solutions out there, then I
will propose an s-expression-based substitute for stream-wiki, and
some way to
Dear all,
The Chicken development snapshot script has been adapted to Chicken
4. From now on, Chicken 4 snapshots will be built and linked to on the
development snapshots page:
http://chicken.wiki.br/dev-snapshots/
New snapshots will be built when the Chicken version is increased in
Hello,
As Elf pointed out, the 3.5.0 release was botched because too many
untested modifications were made to it. The current development
snapshot, 3.5.5 includes bug fixes for some of those issues, although
I am not convinced of the stability of srfi-18, and someone reported a
segmentation
Hi Felix,
Can you copy the current trunk into an old-stable branch (or maybe
in the release/3 branch)? I would like to make one or two more
releases of the 3.x Chicken by the end of the year. Thanks,
-Ivan
felix winkelmann [EMAIL PROTECTED] writes:
Hi!
If possible, new features
The (compile... and (install... forms are actual shell commands,
while the rest is metadata. I am not saying they must be in separate
files, but they are semantically different, so you can't just mash
them together like that.
-Ivan
Shawn Rutledge [EMAIL PROTECTED] writes:
On Mon, Apr
You don't actually need to list the documentation files twice in the
arguments to install-extension. It is only necessary to list them in
the `documentation' property. This is just legacy from older versions
of chicken-setup. It would be pretty easy to add an -examples-path
option to
Hi Mario,
How do you propose this is handled? The situation below occurs
because 501 6 (obviously), so chicken-setup thinks that 1.501 is
newer than 1.6.x. My solution would be to remove releases and
prerequisites of the form x.xxx because such a versioning scheme is
idiotic. But I am open
and consistent representation. You can't go from
release 1.16 to Aleph.XVII and expect that chicken-setup would know
what to do.
-Ivan
Leonardo Valeri Manera [EMAIL PROTECTED] writes:
On 15/04/2008, Ivan Raikov [EMAIL PROTECTED] wrote:
The versions egg uses the same (sane) principle of version
Hello,
I have changed the symbol-string procedure to copy the string
associated with its argument. There should be a new development
snapshot available tomorrow, or you can check it out from SVN.
-Ivan
Peter Bex [EMAIL PROTECTED] writes:
Hi all,
According to Elf the main Chicken
Yes, that's exactly what I have been trying to say. If you use the
same consistent versioning format, then chicken-setup will work
correctly, regardless of whether the format is x.x.x or x.xxx, or
whatever. But if you switch from one format to another, then you risk
messing up the version
I saw it was updated, and I assumed it was you, but the svn log
shows otherwise. Praise withdrawn :-)
-Ivan
Elf [EMAIL PROTECTED] writes:
i did? i didnt
-elf
On Tue, 11 Mar 2008, Ivan Raikov wrote:
You remembered to update NEWS, also. Good developer! :-)
-Ivan
Elf
Okay, I see what you mean now. I think it might be possible to
introduce separate actions or stages in chicken-setup, but I do not
want to make any more changes right now, because I need to deal with
the side-effects of introducing the -install-prefix option.
I believe it would be easy to
workarounds: the express purpose of the
-install-prefix option is for sandbox-type installation.
-Ivan
Leonardo Valeri Manera [EMAIL PROTECTED] writes:
On 02/03/2008, Ivan Raikov [EMAIL PROTECTED] wrote:
What you are referring to is the _Chicken_ install prefix,
i.e. where the Chicken
I was wrong about that, the value of CHICKEN_REPOSITORY is accessed
through the parameter repository-path, and the -R option works as
expected. But if -destdir is specified, then the repository becomes
{destdir}/lib/chicken. -destdir always overrides the repository path,
hence the confusion. I
You can use the svn lock command, but I suppose there isn't so much
danger of modifications to the release/2 branch.
-Ivan
felix winkelmann [EMAIL PROTECTED] writes:
I've created the link. I don't know how to lock release/2 with svn
and would rather avoid that to make it possible to
[EMAIL PROTECTED] writes:
On Mon, Feb 25, 2008 at 2:48 PM, Ivan Raikov [EMAIL PROTECTED] wrote:
I have added two options to chicken-setup: -build-prefix and
-download-dir. build-prefix is where chicken-setup creates a temporary
directory, unpacks the egg and then compiles it. download-dir
I have added two options to chicken-setup: -build-prefix and
-download-dir. build-prefix is where chicken-setup creates a temporary
directory, unpacks the egg and then compiles it. download-dir is the
directory where downloaded egg files are saved. build-prefix defaults
to the value of the
Hello,
If you want, post your patch to this mailing list before committing,
and I can make sure it doesn't break the Unix builds. I don't have
Windows or MSVC, so I cannot test the MSVC build, but at least I can
make sure there are no accidental breakages of something else.
-Ivan
Ashley
Hi all,
It seems that trac.callcc.org is down most of the time I try to
access it. Either I get a 500 error, or the HTTP request times out
after a very long time. Is this instability inherent in Trac, or is
there something peculiar about this particular installation? In either
case, we need to
Hi Felix,
I don't believe I have access rights for milestones, so if anyone
can grant me those, I can start working on a tentative roadmap for the
next release. I have also created a wiki page for roadmap proposals
and discussions:
http://chicken.wiki.br/roadmap
The idea is to use the wiki
I am also still interested in packaging Chicken eggs for Debian. But,
to add to your list of issues, the current version of Chicken in Debian
testing is 2.5. There is a wishlist item filed to upgrade Chicken to
2.7, but so far no response on part of the package maintainer. So we
will either
:
On 9/11/07, Ivan Raikov [EMAIL PROTECTED] wrote:
Hello, Nelson,
You can look at the Debian packaging scripts I wrote for some eggs
here:
http://www.irp.oist.jp/raikov/chicken-eggs-debian.tar.gz
Let me know if you have any questions about those scripts.
Thanks!
Well
Famous last words. ;-)
Peter Bex [EMAIL PROTECTED] writes:
It can never be worse than autohell.
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-hackers
Okay, wow, I didn't know there was so much drama involved in this
:-) I assumed that Chicken used Automake/Autoconf, the way God
intended, and since I have extensive experience with those, I didn't
think there would be a problem adding the Debian files to the dist
target. But I'll learn CMake,
No, I never tested the library in Windows command prompt or
MSVC. I like my POSIX conveniences too much. But of course, Chicken is
a vastly more complex program, so I am sure yours are perfectly
legitimate grievances. I was just curious to hear what problems people
have encountered, since I
42 matches
Mail list logo
