On 8 Mar 2011, at 23:37, Andy Wingo wrote:
> Everyone appears to want gensymmed names. OK! Let's consider this to
> be a bug, and that at some point in the future, Guile will start
> gensymming this names.
I want a syntax that allows one to explicitly choose which macro-bound
variables to expo
Hi,
Bruce Korb writes:
> So, this should go under:
> #if GUILE_VERSION > 20 // anything after 2.0, e.g. 2.0.1 ??
Rather use AC_CHECK_FUNC.
Thanks,
Ludo’.
On Wed 09 Mar 2011 10:33, Hans Aberg writes:
> I want a syntax that allows one to explicitly choose which macro-bound
> variables to export, but otherwise, they should never be visible outside
> the macro (i.e., be uninterned). When exported, they will just have the
> name indicated.
You have th
Greets,
On Wed 09 Mar 2011 11:07, l...@gnu.org (Ludovic Courtès) writes:
> Bruce Korb writes:
>
>> So, this should go under:
>> #if GUILE_VERSION > 20 // anything after 2.0, e.g. 2.0.1 ??
>
> Rather use AC_CHECK_FUNC.
You'd have to check for (ice-9 eval-string) as well, added at the same
ti
Hi Andreas,
Andreas Rottmann writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hi,
>>
>> Andy Wingo writes:
>>
>>> On Sun 06 Mar 2011 23:26, l...@gnu.org (Ludovic Courtès) writes:
>>>
Andreas Rottmann writes:
> The expansion of `define-inlinable' contained an expression, whic
On Sun 06 Mar 2011 23:27, l...@gnu.org (Ludovic Courtès) writes:
> I’ve pushed a variant of this patch.
Sorry for the delay in responding. There was actually a more general
fix. I pushed the following on top of your patch:
commit df1297956211b7353155c9b54d7e9c22d05ce493
Author: Andy Wingo
Dat
On Tue 01 Mar 2011 20:20, Mark H Weaver writes:
> Daniel Llorens writes:
>> I tried to look into SCM_VALIDATE_REAL per the comment, I didn't get
>> far.
>
> Yes, SCM_VALIDATE_REAL (defined in validate.h) requires that the tested
> value be an inexact real, i.e. floating-point. It will reject ex
On Thu 03 Mar 2011 18:50, l...@gnu.org (Ludovic Courtès) writes:
> Do Fedora & co. move ‘.so’ to dev packages too?
Yep.
Andy
--
http://wingolog.org/
On Thu 03 Mar 2011 14:16, l...@gnu.org (Ludovic Courtès) writes:
> Andreas Rottmann writes:
>
>> I wonder how this generally should be handled -- I think the most
>> appropriate way would be to commit any changes that can go into the
>> stable release into stable-2.0 (only), and then, at "conveni
Andy Wingo writes:
>> SCM_NUMBERP, SCM_NUMP, and SCM_INEXACTP ought to be deprecated, and
>> replaced with internal versions.
>
> OK, but in master only please.
Yes, of course, makes sense :)
>> They check only for representations
>> supported by the core implementation, and do not properly sup
10 matches
Mail list logo