On Tue 21 Dec 2010 04:09, Noah Lavine writes:
> The attached patch compresses the objcode representation a bit, then
> adds space for a native code pointer. The whole thing ends up being
> four words, as it is now.
I applied this, then applied some fixes, and after a rebase your patch
went away
On Tue 07 Dec 2010 11:33, Andy Wingo writes:
> The new R6RS support is great. However we are currently pulling in (rnrs
> base) into the set of modules needed by the compiler, because (language
> assembly compile-bytecode) uses open-bytevector-output-port, and the
> ports impl gained a dep on bas
Hey list,
On Tue 07 Dec 2010 11:19, Andy Wingo writes:
> * Blocker bugs for 2.0
>
>- See if objcode space can be reserved for native code -- Andy / Noah
I would still like to do this, for 1.9.15 if possible.
>- The guile <-> unistring escaping issue -- ?
Ludovic is our hero!
> * Wo
Hello!
Andy Wingo writes:
> On Tue 07 Dec 2010 11:33, Andy Wingo writes:
>
>> The new R6RS support is great. However we are currently pulling in (rnrs
>> base) into the set of modules needed by the compiler, because (language
>> assembly compile-bytecode) uses open-bytevector-output-port, and t
Great!
Noah
On Thu, Jan 27, 2011 at 7:12 AM, Andy Wingo wrote:
> On Tue 21 Dec 2010 04:09, Noah Lavine writes:
>
>> The attached patch compresses the objcode representation a bit, then
>> adds space for a native code pointer. The whole thing ends up being
>> four words, as it is now.
>
> I appl
Hi,
On Thu 27 Jan 2011 14:28, l...@gnu.org (Ludovic Courtès) writes:
> A potential problem is that (rnrs io ports) uses bytevectors, defined in
> (rnrs bytevectors), so we would perhaps need an (ice-9 bytevectors) as
> well[*], and a new node in the manual for each, etc.
Currently (rnrs bytevect
On Thu 23 Dec 2010 06:01, Mike Gran writes:
> To avoid the truncated print on the ,backtrace, I find
> myself often typing ",bt #:width 240". Can I alias
> the REPL commands?
Not currently, but patches accepted :) In this case though you might
want a separate option to change the default width
Hi Kan-Ru,
On Tue 04 Jan 2011 10:23, Kan-Ru Chen writes:
> I ran the sputniktests[1] from google using the attached guile-es-parse
> script, which only tests the parser.
>
> === Summary ===
>- Ran 5246 tests
>- Passed 4410 tests (84.1%)
>- Failed 836 tests (15.9%)
Excellent test c
Hi all,
When I was looking at this a while ago, it looked like a big issue
(possibly *the* big issue) with Guile's parser is that it doesn't do
automatic semicolon insertion. (In Javascript, semicolons are optional
in certain contexts, when the place where the semicolon would be is
followed by a n
On Fri 07 Jan 2011 19:52, Mike Gran writes:
>> Guile needs immutable strings.
>
> How is this different from read-only strings?
Seems to be the same. We should have read-only string API though;
currently there is only substring API. One should be able to allocate a
read-only string directly, l
Noah Lavine writes:
> Hi all,
>
> When I was looking at this a while ago, it looked like a big issue
> (possibly *the* big issue) with Guile's parser is that it doesn't do
> automatic semicolon insertion. (In Javascript, semicolons are optional
> in certain contexts, when the place where the semi
Hi!
Andy Wingo writes:
> On Thu 27 Jan 2011 14:28, l...@gnu.org (Ludovic Courtès) writes:
>
>> A potential problem is that (rnrs io ports) uses bytevectors, defined in
>> (rnrs bytevectors), so we would perhaps need an (ice-9 bytevectors) as
>> well[*], and a new node in the manual for each, etc
Hello again,
I've run into another issue with the parser that should be addressed
in the documentation (or the code?).
How do you match a character that is used in the PEG grammar, like
"["? Can you only define such matchers via s-expressions?
Noah
On Thu, Jan 27, 2011 at 12:17 AM, Noah Lavine
13 matches
Mail list logo
