Hello!
Thanks for working on this!
"Andy Wingo" writes:
> +#if BUILDING_LIBGUILE && HAVE_VISIBILITY
> +# define SCM_API extern __attribute__((__visibility__("default")))
> +#elif BUILDING_LIBGUILE && defined _MSC_VER
This should be:
#if defined BUILDING_LIBGUILE && BUILDING_LIBGUILE && HAVE
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Neil Jerram writes:
>
>> FYI I've added a mingw32 compile to my automatic overnight builds,
>> with output going to http://www.ossau.uklinux.net/guile/snapshots.
>
> Cool!
>
> Maybe you could email the output to `gu...@autobuild.josefsson.org' s
Heya Ludo,
On Tue 26 May 2009 19:10, l...@gnu.org (Ludovic Courtès) writes:
> "Andy Wingo" writes:
>
>> +#if BUILDING_LIBGUILE && HAVE_VISIBILITY
>> +# define SCM_API extern __attribute__((__visibility__("default")))
>> +#elif BUILDING_LIBGUILE && defined _MSC_VER
>
> This should be:
>
> #if d
Hey!
Neil Jerram writes:
> I've added an incantation to do that, so hopefully that will happen
> automatically from tonight.
Nice, thanks.
> Should we also have something in the version information to make clear
> that the code being built is a Git head and not a released version?
It's obviou
Andy Wingo writes:
> But I guess that we want to support -Wundef or something, and this is in
> a public header, so I suppose you are right :)
Exactly.
>> Also, I'd have preferred `_GUILE_WITHIN_GUILE', which is clearly in
>> Guile's name space, and is similar to GMP's `__GMP_WITHIN_GMP' ("rule
On Tue 26 May 2009 00:22, l...@gnu.org (Ludovic Courtès) writes:
> However, this relies on eval-after-read semantics. That is, if the
> whole file is read at once, *then* evaluated, that won't work, right?
Or read at once, *then* compiled, *then* evaluated; or even, read one
expression at a time
Hey folks!
So, IMO we need to start pushing towards a release. How about getting a
1.9.1 out soon?
My feeling is that the current feature set in master is ready for a
release. We could just distcheck and that's that. (I tried distcheck
today at work, and it worked fine.)
But there are a few feat
> From: Andy Wingo
>
> On Tue 26 May 2009 00:22, l...@gnu.org (Ludovic Courtès) writes:
>
> > However, this relies on eval-after-read semantics. That is, if the
> > whole file is read at once, *then* evaluated, that won't work, right?
>
> Or read at once, *then* compiled, *then* evaluated;
Hi Andy,
> R6RS library support:
> No code yet. Julian? :-)
Yeah... As I mentioned on IRC, I punted temporarily on that while I
was rewriting the parser for my CSS library. Just yesterday, though,
I started doing some initial work towards adding version information
to modules and the module-
> Hey folks!
>
> So, IMO we need to start pushing towards a release. How about getting a
> 1.9.1 out soon?
>
> Unicode:
>Code shaping up, needs review and R6RS-libs. Unclear how much will be
>in shape for 2.0. Acceptable to ship with only the finished parts.
>
The big steps to hit a be
Hello Andy!
This all sounds like an excellent plan to me!
In practice, that would mean making the first release on June 15th,
right?
Ludo'.
Hi Guilers,
While looking over the prerequisites for the proposed SRFI-100, I came
across SRFI-98, which seemed like pretty easy win for Guile. So I did
a quick implementation on the subway -- find it attached. I'll write
up unit tests and docs if people think it's suitable for integration.
Re
12 matches
Mail list logo
