> Dear All,
>
> is it somehow possible (ie via macros) to have a line in a scheme source code
> file being a comment line by default and only when a certain symbol or group
> of symbols is starting a line it is an uncommented / evaluated line?
> Basically, the reverse of a normal source file
> Hello everyone!
>
> My name is Miguel, and I am interested in developing in Chicken Scheme.
>
> I just created a toy project to put in practice what I have been
> learning in the Little Schemer and SICP books, you can find it here:
>
> https://github.com/MigAP/simple_db
>
> It is a simple
> integer64type
> unsigned-integer64type
> A fixnum or integral flonum, mapping to int64_t or uint64_t. When
> outside of fixnum range the value will overflow into a flonum.
>
> [...] (Numbers between 2^62 and 2^64-1 have gaps.)
>
> ---
>
>
> First of all I don't understand why it's documented as
I just recall that we added line-number info to evaluated code,
this may also have an impact. You can measure the load-time
(just load a large source file) to check whether this is the case.
Evaluation performance should not have changed much, I think.
felix
> Hello, I've tried the git version (2024-02-23, compiled with LLVM-17
> clang, on a Debian 12 / linux 6.6.x). While csc and the executables it
> generates are a bit faster, running my program under csi is now twice as
> slow compared to the latest release (5.3.0).
>
>
> Now before I engage in
> We have a (32-bit, fwiw) C program that we are attempting to augment with a
> CS function. The program runs in ~17 native threads, but our function only
> runs in one of those threads. We call
>
> CHICKEN_initialize(0, 0, 0, C_toplevel);
> CHICKEN_run(C_toplevel);
>
> after the thread
> Aha, so as long as something is wrapped we don't see the same kind of
> inlining.
Correct.
> So what would this look like? I can see fx+ above, which uses
> `chicken:fx+` (prefixed, 2-arity) and foldr to accomplish its multi-arg
> case. Is adding `(inline-file)` to the srfi-143.egg enough
> 1. The egg itself is not compiled with -O3, whereas if I link to
> (chicken fixnum) I believe that these procedures will be inlined by the
> CHICKEN compiler when the arrays egg is compiled with -O3 or higher.
That's correct. As -O3 implies "unsafe", the compiler can just ignore
type checks
>
> ;; a simple un-hygienic macro that sets p to a lambda expression
> ;; using define-er-macro - errors out on lambda no args
> ;;
> ;; a lambda one arg is fine ...
> [...]
Hi!
Sorry for the later eply, but I'm not familiar with the code - have you tried
to contact
the author of the
> I tried your code but I got all kinds of compile errors. Sorry, but it's
> gotten to be too much effort to just open a file.
Indeed, that's understandable. Sorry for not being able to help, but
we are definitely working on improving this situation for the next
major release of CHICKEN.
felix
> Thanks for the responses. I tried what I could, but it still doesn't work.
> I wrote some code to test if I can open and close a file. The C code works
> but the Chicken code doesn't.
>
> (import (chicken foreign))
>
> (foreign-declare "#include ")
> (foreign-declare "#include ")
>
> (define
> Hi everyone,
>
> I want to read input from a file that contains accented characters in its
> name, and Chicken says that it can't open the file. The source code is
> saved in a UTF-8 encoded text file.
> [...]
> I use Windows, and I run the script in the Command Prompt. Before running
> it, I
I wish you all a merry christmas and a relaxed and fulfilling 2024.
cheers,
felix
> It fails because TIOCSTI is undefined. OpenBSD removed it for security
> reasons.
>
> How could that egg be modified to allow it to compile on OpenBSD?
Hi! Thanks for reporting this - I have added a dummy definition (ioctl 0.4)
for OpenBSD.
felix
> Would it be possible to mark deprecations with alternatives/documentation
> to point users in the new direction?
Yes, next time, such a warning should mention any replacements.
There is also a DEPRECATED file in the sources that lists recent
deprecations.
Thanks for the suggestion.
felix
> How about
> "empty egg-info file, possibly due to an aborted egg-install - please remove
> the file and reinstall the corresponding egg"?
>
> Rationale: Matt's case. check-errors.egg-info was empty, but the
> installation of base64 was failing. If Matt had removed
> check-errors.egg-info and
> That was it. Thanks. I do have to keep running:
>
> find /software/ -name \*.egg-info -empty -delete -print
>
> as check-errors.egg-info seems to be a pervasive problem. Maybe it would be
> worth it to add a defence against this?
>
>
Sorry - wrong patch, this is the right one.
felix
> That was it. Thanks. I do have to keep running:
>
> find /software/ -name \*.egg-info -empty -delete -print
>
> as check-errors.egg-info seems to be a pervasive problem. Maybe it would be
> worth it to add a defence against this?
>
Attached is a patch that catches at least this case.
felix
> On 28/06/2023 14:09, felix.winkelm...@bevuta.com wrote:
> >>
> >> (define-object-type bar
> >> (field-1 name-of-library#foo)
> >> (field-2 name-of-other-library#some-other-type))
> >>
> >> ...even though calling symbol-value on those symbols at run time works
> >> just fine. It seems
>
> (define-object-type bar
>(field-1 name-of-library#foo)
>(field-2 name-of-other-library#some-other-type))
>
> ...even though calling symbol-value on those symbols at run time works
> just fine. It seems that the symbols imported into the environment at
> macro expansion time are handled
> I want to get mouse clicks from the ui scene but I cannot access the ui
> camera. In hypergiant/window.scm the ui camera is found in *ui-camera* but
> this is not exported. When I added it to the exports I was able to see the
> mouse clicks with this:
>
> (get-cursor-world-position *ui-camera*)
> It looks like I should be able to do line drawings with line-mesh. The spec
> in the docs is:
>
> [procedure] (line-mesh POINTS [mode: MODE])
>
> Create a non-indexed mesh of POINTS. MODE should be a valid argument to
> mode->gl, defaulting to #:line-strip.
>
> But I can't figure out what POINTS
> I'm trying to compile the simple.scm example from hypergiant statically
> using csm. Is this possible?
>
Hi, again!
Can you try the attached alternative .egg file for
hyperscene? Just invoke
chicken-install -r hyperscene
and replace the .egg file with the one in this mail.
This should
> I'm trying to compile the simple.scm example from hypergiant statically
> using csm. Is this possible?
>
> [...]
(followup)
That default to dynamic linkage was chosen to circumvent a csc
limitation, I'm afraid. Hyperscene passes several .c files on the
cmdline which doesn't work with "-c"
> I'm trying to compile the simple.scm example from hypergiant statically
> using csm. Is this possible?
>
> all.options:
> -program simple -C -I/usr/include
>
> simple.options:
> -L -L/usr/lib/x86_64-linux-gnu -L -lepoxy -L -lGL -static -L -static -L -lm
> -L -ldl -link hyperscene
>
> I've tried
> Is there a desire to stick to r5rs features only in the chicken-core
> expander, or is the intention to fold the R7RS / SRFI 46 features back
> into the chicken-core expander at some point in the future?
I haven't thought about it, and the extensions for R7RS are from Peter
(I think). We could
> Hi,
>
> > I have updated the wiki page for the event at
> >
> > http://wiki.call-cc.org/event/village-chickens-2023
> >
> > with some info regarding location and travel. Please
> > contact me if you have any questions or need assistance.
> >
> > See you in June!
>
> I've just seen this.
>
>
Hi!
I have updated the wiki page for the event at
http://wiki.call-cc.org/event/village-chickens-2023
with some info regarding location and travel. Please
contact me if you have any questions or need assistance.
See you in June!
felix
> Also I'm from Python land, where exceptions are never resumable. The YouTube
> talks about Common Lisp rave about conditions, mostly in the context of
> interactive development ("Call a function that doesn't exist yet!" etc). Now
> here I see exceptions and conditions, and they are well
> >> If breaking 5.X | X < latest is a concern, this means
> >> current-milliseconds must stay in 6.x and can only be removed in
> >> 7.x?
> >
> > Hm I don't see how that follows. Removing current-milliseconds in 6.x
> > doesn't break anything 5.x.
>
> Right, but just because that's already kinda
> Hi everyone. Sorry if this is an obvious question, but can I *not* compile an
> extension statically?
>
> In other words, I’m trying to build chickadee, and I believe it's taking
> around twice as long as expected because it is building every egg dependency
> dynamically and then again
is what I wish to all of you!
cheers,
felix
Hi!
I have added a wiki page for our next CHICKEN meeting:
http://wiki.call-cc.org/event/village-chickens-2023
The page contains some more details. Please make sure to announce
your participation until mid-January, so we can plan the event
accordingly.
cheers,
felix
Hello!
I'd like to organize a CHICKEN meeting at the start of June
in the place where I live. Our regular live meetings were
always a lot of fun, and I think it would be nice to pick this
tradition up again.
The plan is currently to have the event on the first weekend of
June 2023. The location
> > Actually, perhaps the best way would be to use a custom build
> > using csm to build the components of the egg. A little bit of
> > inventiveness might be required, but I think it should be possible.
>
> This would make the egg depend on csm. I don't mind this for programs,
> but for eggs that
> > Actually, perhaps the best way would be to use a custom build
> > using csm to build the components of the egg. A little bit of
> > inventiveness might be required, but I think it should be possible.
>
> This would make the egg depend on csm. I don't mind this for programs,
> but for eggs that
Actually, perhaps the best way would be to use a custom build
using csm to build the components of the egg. A little bit of
inventiveness might be required, but I think it should be possible.
I added a "-compile-imports" to csm today to force import libs to
be compiled, which may be a start.
> Would it be possible to add a feature something like this?
>
> (extension foo.bar
>(source "bar.sld")
>(auto-dependencies) ; <-- The new feature.
>(csc-options "-R" "r7rs" "-X" "r7rs"))
>
> auto-dependencies would compute the deps by traversing the given source
> file. It would look
> Over time I have amassed a small collection of useful (to me)
> procedures. I have a folder, containing several files each of which
> defines a library (equivalent to a module in chicken, I think). I set
> the environment variable CHEZSCHEMELIBDIRS to point at this folder and
> then I can do
Hello!
Vasilij found a security issue with the way egg-information
files are created during installation of an extension package.
Currently, escape characters in the .egg file may be used to
perform arbitrary OS command injection due to the method the
egg metadata is created and installed in the
>
> ...aaand I've erred once more. Sorry, the following is the correct link for
> srfi-143:
>
> (srfi-143
> "https://git.sr.ht/~dieggsy/srfi-143/blob/master/srfi-143.release-info;)
>
Fixed.
felix
> Hi,
>
> I've just moved all my eggs to sourcehut. Here are the new locations. I've
> run all of them through test-new-egg again just in case.
>
> (chalk "https://git.sr.ht/~dieggsy/chalk/blob/master/chalk.release-info;)
> (chibi-generic
>
> 1) The SRFI-18 egg has not reached version 1. Which threading egg do you
> recommend for my simple case?
There is really just this one egg for threading. The version number
you should ignore - the code is in production use for ages.
felix
> Dear Wolf,
>
> thank you for testing. I am currently using -O4 as the performance gab
> between -O3 and -O4 is rather large (likely because of those safety
> measures). You are probably right that -O3 is more sensible; I will adapt
> this for the next version and think about how to provide a
> What I would like to know is whether the opposite is true: if I define
> a custom name to refer to a pre-defined procedure, can I expect it to
> get the same kind of special treatment from the compiler? For example,
> if I put the following expressions in my code:
>
> (define ≤ <=)
> (define
> This is on ubuntu, chicken 5.3:
>
> Test code:
> (module yamltest *
> (import scheme
> chicken.string
> yaml)
> (write (yaml-load "test.yaml")))
>
> > csm -static -program yamltest
> '/home/ubuntu/data/buildall/w23-0-ck5.3/bin/csc' '-o' 'yamltest' '-I'
>
> ck5 csm -program kvpub -static
> '/home/mrwellan/data/buildall/ck5.3/bin/csc' '-c' '-static' '-J'
> '/home/mrwellan/data/kvpub/mtargs.scm' '-I' '/home/mrwellan/data/kvpub'
> '-C' '-I' '-C' '/home/mrwellan/data/kvpub' '-unit' 'mtargs'
> '-emit-link-file' 'mtargs.link' '-o' 'mtargs.o'
>
> Dear felix,
>
> after coming back to this function and the associated issues regularly, I
> revised my opinion on integrating"fp+*" into (chicken flonum), given it uses
> the C99-fma function. On the one hand, this operation is so fundamental in
> numerical computations that it warrants a
> On Mon, Mar 21, 2022 at 5:19 AM wrote:
>
>
> > Sorry for the overly late reply. I'm not too familiar with cygwin, what
> > should the tests report here? The cond-expand for "windows" should trigger
> > on cygwin, how is it handling the permission bits (as compared to "raw"
> > Windows systems)?
> Bonjour,
>
> Currently, Chicken Scheme 5.3.0 builds without problem on Windows 10 Home
> (21H2 64-bit) with a recently updated Cygwin64.
>
> The check fails during the POSIX test when testing file system permissions.
> This failure is expected, but the check process dies. The error is farther
>
> Chris Brannon wrote:
> > I've been working on something along those lines myself, in fits and
> > starts. I haven't gotten too far with it, but my basic idea is to make
> > a library of data structures and functions suitable for creating
> > ed-style interfaces where the basic metaphor is a
> Hi,
> I am new to chicken and got stuck trying to do buffered inter-process
> communication.
> Could someone give me a hint why in the sample code below `copy_b`
> freezes whereas `copy_c` works as expected?
> Thanks!
>
As read-buffered only returns the data buffered by the last read operation,
> Under these assumptions I concluded that it should be possible to
> detect what has been matched by checking whether the indices of the
> assoc. list are valid in the current match object, stopping after the
> first successful test.
>
> (import (chicken irregex))
> ;;; swapping fred and wilma
>
> I hope this is the right place to send this to, but here we go. For our
> project, we wanted support for some modern C++-features in the "bind" egg:
>
> 1. nested namespace definitions: instead of namespace A { namespace B {
> ... } }, C++17 allows writing namespace A::B { ... }
> 2. typed
> Hello Robert,
>
> you are right, you can not directly call procedures from modules/units
> compiled with -block.
>
> A trick I used to "export" procedures was to have two compilation units
> (I used modules for both). One, the "hook", defining and exporting top
> level bindings, which is not
Everybody!
I wish all of you a very happy christmas.
felix
> In general, this lack of specificity and consistency when it comes to how
> CHICKEN deals with files and modules in the smaller scale is something that’s
> keeping me from being truly productive with the environment; I just can’t come
> up with a flexible way to organize my projects that can
> Hi Felix,
>
> I did not know about csm (or perhaps forgot it's existence?). Anyhow it
> seems like a potentially much better solution than a
> hand-maintained Makefile. I've tried it on a couple code bases and I'm
> running into a few issues, some are just cruft in the code but two cases
> I'm
> Wow, that seems to have fixed it. Thanks!!
Also, I will not tire to point out that "csm" is always a viable alternative!
:-)
felix
> I went ahead and completed the minimal example build including the use of
> .import.o files to enable using modules in evals. See attached tar. It
> works fine which implies that, as you suggested, I have something wrong in
> my build system.
Thanks for the example code, this is really helpful
> Thanks Felix for looking. Both run with -:d and attached.
>
> I only see the following loading calls in dashboard.log:
>
> ; loading /home/matt/data/buildall/ck5.2/lib/chicken/11/
> chicken.time.import.so ...
> [debug] loading compiled library
>
> On Fri, Nov 12, 2021 at 3:47 AM wrote:
>
> > > Update. I found that removing the *.import.scm files causes the problem
> > to
> > > also occur when running the executable in the directory where compiled.
> > > However the non-gui executable still works fine. Why would a compiled
> > > Chicken
> Update. I found that removing the *.import.scm files causes the problem to
> also occur when running the executable in the directory where compiled.
> However the non-gui executable still works fine. Why would a compiled
> Chicken program be reading the import.scm files at run time?
This can
> Dear Felix,
>
> Thank you for the patch. I built the current git head with your patch.
> After importing chicken.flonum, I get the following error when calling fp*+:
>
I'm terribly sorry. I'm an ass, I didn't even test it in the interpreter. Please
find attached a revised patch.
felix
From
Hi!
Here a patch against the current git HEAD, adding support for "fp*+". Please
give it a try, if you want.
This is experimental, if people consider this worthwhile, I can submit it for
adding to the core
system. Note that you still may need passing extra C-compiler options to enable
inlining
> a patch would be great, if it is not too much work. Attached you find three
> assembly language files:
>
> * fma-test_original.s (unchananged csc c to assembly)
> * fma-test_modified.s (modified csc c from previous mail)
> * fma-test_modified_mfma.s (modified csc c and -mfma gcc option)
>
>
> modified code:
>
> 7.378s CPU time, 0/225861 GCs (major/minor), maximum live heap: 30.78 MiB
> 8.498s CPU time, 0/238095 GCs (major/minor), maximum live heap: 30.78 MiB
>
> Both were compiled with -O3 optimization level in gcc.
>
> I am fine with these results given your layout of the internals
> 7.558s CPU time, 0/225861 GCs (major/minor), maximum live heap: 30.78 MiB
> 8.839s CPU time, 0/256410 GCs (major/minor), maximum live heap: 30.78 MiB
>
>[...]
>
> It would be great to get some help or explanation with this issue.
Hi!
I have similar timings and the difference in the number of
Mark,
Many thanks for this thorough analysis. Could you do me a favour?
Could you send me the installation instructions and the
generated chicken-config.h files for each build option you used?
Perhaps that way we can figure out where our various Windows
build configurations are inconsistent.
> On Sat, Aug 14, 2021 at 08:25:21PM +0200, Sven Hartrumpf wrote:
> > Hi.
> >
> > The segmentation violation disappeared after cleaning my build script for
> > chicken.
> > (It contained an old "-mpreferred-stack-boundary=4" in
> > C_COMPILER_OPTIMIZATION_OPTIONS,
> > which I dropped now.)
>
>
> The convention (observed at least by Chibi, Gambit, and Gauche) is that
> each .sld file contains one define-library form.
>
> Gambit can compile something like hello.sld:
>
> (define-library (hello)
>(import (scheme base))
>(begin (write-string "Hello world\n")))
>
> into an object file
> If there are few substantial differences, it would be a boon to writing
> portable code if the same syntax is eventually used as for standard R7RS
> libraries, and the same filename conventions are supported as other R7RS
> implementations (the .sld filename extension for an R7RS library is
>
> I've got a module mymod in mymod.scm:
>
>[...]
>
> However, I can't figure out how to do the same thing with mymod as
> non-shared objects. I tried
>
> csc -c -J mymod.scm
> csc -c mymod.import.scm
> csc -static -o trymod.static mymod.o mymod.import.o trymod.scm
>
> but I got
>
> Undefined
> >
> > (modules species (species ui))
> >
> > declares 2 modules, I"m not sure chicken-install can detect that the
> > extension
> > consists of 2 files, with one module for each.
> >
>
> Does this mean that extensions are not supposed to be composed of more
> than one module?
It is uncommon,
> Exactly what I was looking for!
Feedback is welcome. Should you experience any problems, don't hesitate to
report them.
felix
> Building, testing, and installing all worked out of the box, but I got
> these two warnings while compiling (in red even though they're warnings):
>
>[...]
Hm, I have no idea, but I noticed a couple of suspicious warnings. In fact,
the code doesn't even compile without "-w", which may indicate
Hi!
A first version of "csm" is available, a build system for CHICKEN Scheme
programs:
http://wiki.call-cc.org/eggref/5/csm
Assuming a small set of conventions, this tool can infer dependencies and
necessary
command-line options for a set of source files written in CHICKEN or R7RS
Scheme.
> I have tried removing one of the 2 modules declared in the .egg but I
> have the same problem. When I remove the
> (species ui) import from darwin.scm it compiles and runs the tests
> but of course fails to resolve the symbol at runtime.
>
(modules species (species ui))
declares 2 modules,
> Error: (car) bad argument type:
> |\xcf\xfa\xed\xfe\x07\x00\x00\x01\x03\x00\x00\x00\x02\x00\x00\x00\x11\x00\x00\x00\x90\x06\x00\x00\x85\x00|
>
I haven't analyzed this, but this looks like is the header of a binary object,
so the runtime
system is trying to load a binary, perhaps a import
Hi!
This is to announce the "mdh" egg, an interface to the C++ API of O'Kane's
MUMPS database. The concepts behind it were presented by Luke at the
CHICKEN Coding Jam and produced quite some interest. MDH is a very
easy to use multidimensional key-value store. The code is included in
the egg, the
> chicken install address-info ansi-escape-sequences apropos base64 crypt
> csv-abnf
> directory-utils filepath fmt format http-client
> intarweb json linenoise matchable md5 message-digest moremacros
> pathname-expand postgresql queues regex-case rfc3339 s11n sha1
> slice sparse-vectors spiffy
>
Hello!
We are happy to report that the 2021 coding jam at the previous weekend was
a very entertaining and interesting event. Participation was quite good, we had
excellent talks and presentations and did a very fruitful evaluation of the
2021 state of CHICKEN survey.
Thank you all for taking
Hi, folks!
The CHICKEN Coding Jam 2021 has officially started. Please join
#ChickenCodingJam on irc.freenode.net to participate. Everybody is
welcome!
Visit
http://wiki.call-cc.org/event/coding-jam-2021
for the schedule and up-to-date information about the event.
felix
> I'm trying to compile a small project with some imports (some srfi,
> matchable, and ncurses) to a bunch of *.{c,h} files for easier
> distribution. Following http://wiki.call-cc.org/man/5/Deployment
> compiling the example to a test.c went smooth. However, I'm already
> stuck with
>
> ;
Hi, folks!
This is the now the official announcement of the first CHICKEN Coding Jam,
taking place online from 9th to the 11th of April 2021.
It will be an opportunity to meet and discuss CHICKEN, Scheme, software,
programming, hold talks, do presentations or just get to know each other.
We also
> I've spent a few months evaluating the existing options for C4 and
> making a few myself. From the existing options pstk was the only one
> worth using as it has been around the longest and solves the common GUI
> problems you'd run into. Consider whether a design like ma [1] would
> work for
Hi, Jürgen!
> I suggest, to include a filter routine with two values, the sublist
> which passes the test and the sublist which fails at least into (chicken
> base) which is imported most of the time.
I think depending on SRFI-1 isn't that mauch hassle. On the other hand
we have fundamental
> Hi all,
>
> I've noticed that the documentation for CHICKEN 3 eggs (and also for
> CHICKEN 2 eggs, where we have them) contain a "OUTDATED EGG" warning
> at the top, to warn people away from them.
>
> I'm thinking, maybe we should do something similar for CHICKEN 4
> documentation now. CHICKEN
> Here's a listing of all eggs with
>
> - egg name
> - description
> - license
> - latest egg version number for Chicken 5
> - latest egg version number for Chicken 4
> - link to egg documentation (wiki) and git repo for both versions
> - color indicator saying whether each version is up to date
I wish all of you a very happy christmas. Many thanks to all who
have participated, contributed, followed or just used CHICKEN and
supported this project in one way or another.
May your parens always be balanced!
felix
> I'm not doing any call/cc or non-local exit shenanigans, but the code
> uses srfi-18 threads and does I/O over TCP. As I understand it, srfi-18
> is implemented using continuations. Will that cause problems with my
> with-lock function? I'm thinking that a thread that has aquired the lock
> in
> 1. Are there any problems with creating a condition (as in exception,
>not srfi-18 condition variable) in one thread and raising it in one
>or more other threads?
No problem here, I'd say, data can be freely exchanged between threads,
since they share a global address space. A condition
> Is there a way to figure out if running in csi at runtime without using
> cond-expand?
>
You can test "(feature? #:csi)" to figure out whether the current executable is
"csi".
felix
> Hi *,
>
> I asked a question on stackoverflow (link below), but didn't get any answer
> so far. If anyone knows how to deal with it, don't hesitate to let me know
> (whether per mail or per SO answer).
>
I fixed the two bugs you encountered - one was caused by a non-existent internal
library
> Thanks for the suggestion! With this fix, I get as a result of
>
> (import (test-eval))
> (my-eval)
>
> an error which is shown below. Any ideas?
The reference to "delq" is an error in the r7rs egg, but the other error
is somewhere deep in the module system. I'm currently investigating
this -
OS: OpenBSD 6.5
Hw: x86_64
cc: gcc version 4.2.1 20070719
Build, check and install works, but pastiche depends on
sql-de-lite which needs to be patched for 5.2.0. I tried with
awful, which also a bunch of dependencies, which worked fine.
felix
> crypt egg helped a ton. Thank you for that. I'm also running into a
> missing "sparse-vectors" egg.
Should be available any moment.
felix
> Matt Welland and I are porting some existing code to chicken 5. We ran
> into some eggs that we are using that we would like in chicken 5:
>
> csv-xml
> crypt
>
> We also needed the autload, pathname-expand and dbi eggs.
> The diff for pathname-expand egg is here:
>
Folks,
I wish all of you a very happy christmas and a fulfilling and pleasant new
year!
cheers
felix
> > All of these Schemes start up instantly and due to their simplicity
> > are the easiest to embed into C with no external dependencies. Their
> > internals are easy to modify as needed. But they are also the slowest
> > interpreters available. They don't even have a bytecode compiler; they
> >
1 - 100 of 1820 matches
Mail list logo
