Hi Mads,
Glad to see I'm not the only person who's building Guile for Windows!
For the gEDA project, which uses Guile quite extensively, we've for
quite some years had a recipe-based cross-build system called "minipack"
that's use for cross-compiling Guile and the geda-gaf electronic design
packa
Hi Andy,
All of this stuff sounds great, and I can't wait for it to be available!
Can I please request an addition to your to-do list: a document that
explains what changes to libguile-using programs will be required?
Getting people from 1.8 to 2.0 is hard enough, and soon Guile will be
*two* majo
l...@gnu.org (Ludovic Courtès) writes:
> Hi Peter,
>
> Peter TB Brett skribis:
>
>> This is going to sound like a daft question, but: is there any reason
>> that the thread that calls 'touch' needs to be the same thread that
>> calls its continuation
This is going to sound like a daft question, but: is there any reason
that the thread that calls 'touch' needs to be the same thread that
calls its continuation?
I.e. why does there need to be a special "main thread"? Can't "picking
up a job blocking on touch" just be another task allocated to th
Daniel Llorens writes:
> The only generalized-vector-? function that doesn't have a direct
> array-? correspondence is generalized-vector-length. However, even for
> arrays of rank > 1 it is often convenient to have a function such as
>
> (array-length a) = (car (array-dimensions a))
>
> or maybe
Andy Wingo writes:
> I use git, from the command line and from Emacs. When I use it from
> Emacs, I use magit: http://philjackson.github.com/magit/
>
> I mostly use magit to commit, and otherwise the command line to update,
> rebase, etc. I use gitk sometimes to get a graphical representations
Catonano writes:
> I copied a patch from my gmail web inerface and pasted in a local file, but I
> discovered I had to run dos2unix on it in order to git to process it properly
> (see http://stackoverflow.com/questions/1821267/
> how-can-i-apply-a-patch-file-in-git) and then I also run into anoth
Andy Wingo writes:
> On Mon 23 Jan 2012 22:03, Mark H Weaver writes:
>> Your priorities are reversed from what they ought to be.
>>
>> What you _should_ be worried about is making commitments in our API that
>> we must continue to support forever. This is a _real_ problem, since it
>> constrain
David Kastrup writes:
>> * I still wouldn't be surprised if `local-eval' does the wrong thing if
>> (current-module) is different from what it was when the associated
>> `primitive-eval' was called.
>
> Before anyone even _defines_ what the "right thing" would be, there is
> little point in
