Hi,
I've gone through the code for fluids to understand it. And how it relates to
unification variables.
Some facts for fluids:
* Allocation is slow, can be made faster but still it seams to be slow
- Allocates on the heap
- uses a mutex
Hi,
On Tue 25 May 2010 23:42, l...@gnu.org (Ludovic Courtès) writes:
> There’s now a new (sxml match) module, containing Jim Bender’s excellent
> SXML pattern matcher (released under the X11/MIT license):
Cool :)
> I integrated the doc in the manual. Unfortunately it can’t be made to
> appear
Hey Andy,
>> We could make this more general, as the r7 committees are wont to do: if
>> #! is followed by whitespace or /, then read as a block comment;
>> otherwise read one token. In our case, we would read #!foo as #:foo. I
>> don't think this change would affect anyone. What do you think?
>
>
Hi,
On Wed 26 May 2010 13:16, Stefan writes:
> I've gone through the code for fluids to understand it. And how it relates to
> unification variables.
>
> Some facts for fluids:
> * Allocation is slow, can be made faster but still it seams to be
> slow
Indeed; you don't want to be allocatin
On Wed 26 May 2010 15:02, Julian Graham writes:
>>> We could make this more general, as the r7 committees are wont to do: if
>>> #! is followed by whitespace or /, then read as a block comment;
>>> otherwise read one token. In our case, we would read #!foo as #:foo. I
>>> don't think this chang
Hi Andy!
Andy Wingo writes:
> On Tue 25 May 2010 23:42, l...@gnu.org (Ludovic Courtès) writes:
>> I integrated the doc in the manual. Unfortunately it can’t be made to
>> appear close to the automatically generated doc of (sxml simple), so it
>> actually appears before. I’m open to suggestion
Hi,
On Wed 26 May 2010 16:12, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo writes:
>
>> On Tue 25 May 2010 23:42, l...@gnu.org (Ludovic Courtès) writes:
>
>>> I integrated the doc in the manual. Unfortunately it can’t be made to
>>> appear close to the automatically generated doc of (sxm
Hi,
Andy Wingo writes:
> On Wed 26 May 2010 15:02, Julian Graham writes:
>
We could make this more general, as the r7 committees are wont to do: if
#! is followed by whitespace or /, then read as a block comment;
otherwise read one token. In our case, we would read #!foo as #:foo
Whoops ! Due to my misunderstanding of 'git push' I committed this to
master. I had already committed it to master locally so after I merge
it, I guess it pushed my master changes as well when I was trying to
push my lua branch. Hopefully I didn't mess up anything else. I read
the docs now so it w
Hi!
I’ve (finally) renamed ‘testsuite’ to ‘test-suite/vm’. Please shout if
that’s not to your taste.
Thanks,
Ludo’.
Hi!
No Itisnt writes:
> Whoops ! Due to my misunderstanding of 'git push' I committed this to
> master. I had already committed it to master locally so after I merge
> it, I guess it pushed my master changes as well when I was trying to
> push my lua branch.
I pushed changes after you pushed yo
Hi,
No Itisnt writes:
> On Tue, May 25, 2010 at 3:56 PM, No Itisnt wrote:
>> I agree. Here's a patch that adds (srfi srfi-9 gnu) with
>> set-record-printer! and adds a subsection to the SRFI-9 part of the
>> manual for it.
>> I can go ahead and commit it, if that's OK.
This looks good to me.
BTW, you should always create a local branch when working on something,
even if it may eventually be committed to ‘master’. The reason is that
something else may be pushed before your commit, and if you just run
‘git push’ after that, we’ll end up with a merge commit, which we’d
rather avoid.
So
OK.
> s/GUILE/Guile/ and two spaces after and end-of-sentence period.
How so? Two trailing spaces after the period or two newlines?
Is there a style guide somewhere? I was mainly copying and pasting
from srfi-modules.texi.
> I’d rather call it ‘set-record-type-printer!’ (it prints records, but
>
Hi,
I'm another of the GSOC students--I figured I'd introduce myself since
I may be asking questions on this list. I'm going to be writing a PEG
parser/matcher for Guile. My paperwork is still working its way
through the system so I can't point to any repositories where my code
will be yet, but
15 matches
Mail list logo
