On Wed, 2012-08-01 at 22:59 +0200, Stefan Israelsson Tampe wrote:
> Hi,
>
> The byte-code -> native-code compiler is does serve my needs pretty well
> now. It should really
> soon be possible to add code that will auto compile bytecode versions to
> native versions. The compiler is not perfect and
On Sat, 2012-11-17 at 00:36 +0100, Ludovic Courtès wrote:
> Hello!
>
> As was reported recently by Mark and others, ‘par-map’ would only use
> ncores - 1, because the main thread was stuck in a
> ‘wait-condition-variable’ while touching one of the futures.
>
> The obvious fix is to write ‘par-map
Hi!
Noah Lavine skribis:
> Yes, I agree with everything you said here. I'm torn, because I think that
> in general having more portable Scheme code is good for everyone, and the
> RnRS standards are the best way to do that, so maybe we should just accept
> that the most recent 1 or 2 standards w
> From: Mark H Weaver
> To: guile-devel@gnu.org
> Cc: Michael Gran
> Sent: Sunday, January 13, 2013 10:25 AM
> Subject: Scanning for coding declarations in all files (not just source)
>
Hi Mark,
> I just discovered that Guile is scanning for coding declarations in
> *all* files opened with 'ope
I just discovered that Guile is scanning for coding declarations in
*all* files opened with 'open-file', not just source files.
For source files, we are scanning for coding declarations twice: once
when when the file is opened, and a second time when 'compile-file' or
'primitive-load' explicitly s
Nala Ginrut writes:
>> What about common lisp is scheme a lisp or is CL a scheme :-)
>>
>
> IIRC， someone raised the topic that emerge Clisp into Guile in 2011,
> but what's the status now?
>
>> Anyway to support CL I would think that we need to support placing
>> properties
>> on symbols, e,g.
