-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Andy,
On 05-12-11 21:23, Andy Wingo wrote:
> Heya Ludo,
>
> On Thu 30 Jun 2011 12:44, Andy Wingo writes:
>
>> I think we should add `when' and `unless' to the default
>> environment.
>>
>> They go like this:
>>
>> (define-syntax when (syntax-r
Hello Guile developers,
Despite the long gap since my last email, I have in fact been working
on the compiler project. This email has two purposes: first, to make
sure that I have a basically reasonable design before I work more, and
second, to ask a logistical question.
First of all, I very much
> I guess in general I'd prefer something like Racket's #!lang directives,
> though I'm not opposed to this approach. Dunno!
How about using language directives when available, and trying to
guess the language when not?
And about the directives, what should they be? ',language' is what we
used t
On Fri 01 Jul 2011 23:11, l...@gnu.org (Ludovic Courtès) writes:
> As seen in ccb80964cd7cd112e300c34d32f67125a6d6da9a, there’s a lock
> ordering mismatch between ‘do_thread exit’ and ‘fat_mutex_lock’
> wrt. ‘t->admin_mutex’ and ‘m->lock’.
Filed here: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=
Heya Ludo,
On Thu 30 Jun 2011 12:44, Andy Wingo writes:
> I think we should add `when' and `unless' to the default environment.
>
> They go like this:
>
> (define-syntax when
> (syntax-rules ()
> ((_ test then then* ...)
>(if test (begin then then* ... (if #f #f))
>
> (
So I tried to get hold of the macro binding. So with the following patch
wich should be enogh
for me to make progress porting rackets syntax parse to guile.
Would be very glad if we could find a interface to expose this information
that is sane
and rigid manner. So we should discuss this feature.
Hi,
On Thu 30 Jun 2011 03:24, Andreas Rottmann writes:
> Andy Wingo writes:
>
>> After some thinking, the base thing to do is just to add a warning port,
>> and make warnings (non-fatal informative messages) write to that port.
>> I have done this in the attached patches.
I have pushed patches
Hello David,
On Mon 05 Dec 2011 09:11, David Kastrup writes:
> David Kastrup writes:
>
>>> (symbol-set! #f (string->symbol name) value)
>> (module-define! (current-module) (string->symbol name) value)
Indeed, the module system needs better documentation.
>> Is this somebody's idea of a joke?
Heya BT,
On Thu 21 Jul 2011 08:28, BT Templeton writes:
> * Buffer-local variable support
> * Condition handling, property lists, other new subrs
> * Variable and function aliases
> * Emacs-compatible lexbind
> * Compatibility fixes
> * Most subrs and macros are now written in Elisp
> * Emacs wi
Hello June!
On Sun 12 Jun 2011 03:24, BT Templeton writes:
> What is `*current-language*' supposed to be used for?
It is supposed to be a default language for the compiler and other
things that are interested in languages.
> I see that it's
> set by `(@ (ice-9 eval-string) read-and-eval)' and
On Wed 22 Jun 2011 16:24, l...@gnu.org (Ludovic Courtès) writes:
> (define-syntax pollfd-offset
> (syntax-rules ()
> ((_ n) (* n 8
>
> I guess 8 is really sizeof (struct pollfd), right?
>
> In that case, how about getting it at configure time and exporting it
> from C?
Done, sorta
Hi,
On Wed 22 Jun 2011 23:49, Neil Jerram writes:
> Ian Price writes:
>
>> There's a small aesthetic issue that's been bothering me for a
>> while. Namely, newlines aren't treated like other escape sequences when
>> printed with WRITE.
>>
>> scheme@(guile-user)> (write "\n")
>> "
>> "
>
> I agr
David Kastrup writes:
> David Kastrup writes:
>
>> The module system documentation provides _no_ _clue_ _whatsoever_ about
>> how something like
>> (symbol-set! #f (string->symbol name) value)
>> could be replaced. In fact, the module system documentation provides
>> _no_ _clue_ _whatsoever_ ho
13 matches
Mail list logo
