bornlibra23 writes:
> Thanks Mike for the heads up but the problem I think is with the source code
> itself. I get the same error on linux though it doesnt die there. I
> preprocessed the code & changed the line like so :
>>From (ch) == ' ' | (ch) == '\t') to (ch) == ' ' || (ch) == '\t')
Daniel Kraft writes:
> Lambda arguments are still always dynamically bound, which is quite a
> pity as it inhibits tail-call optimization;
This prompted me to wonder if using fluids is the best way to
implement dynamic binding.
Perhaps I'm forgetting something basic, but surely it's using
`dyna
Andy Wingo writes:
> Hi Neil,
>
> Thanks for the review.
>
> On Wed 22 Jul 2009 23:48, Neil Jerram writes:
>
>> I have two overall questions in mind.
>>
>> - What do you have in mind as regards releasing this? Even though it
>> looks good, I think it would be better to let it mature for a whi
Clinton Ebadi writes:
> Why not eliminate %nil/#nil and replace it with ... '(). This would
> allow elisp to reuse all (or at least most) of the Scheme list functions
> without having to muddy Scheme semantics with special #f/#nil handling,
> but would require a very tiny elisp specific truth pre
Andy Wingo writes:
>> Other things needed would be for instance terminating rest-arguments
>> by %nil rather than '() and the like.
Why is that needed? I.e. Why is it important for a rest argument to
be terminated with %nil instead of with () ?
Neil
Andy Wingo writes:
> Hi Mark,
>
> This is also not a patch review yet :)
>
> On Thu 09 Jul 2009 18:11, Mark H Weaver writes:
>
>> I added the following macros, whose names explicitly state how %nil
>> should be handled. See the comments in the patch for more information
>> about these.
Hi Mark
Hello!
"Michael Gran" writes:
> The branch, master has been updated
>via 77332b21a01fac906ae4707426e00f01e62c0415 (commit)
> from e5dc27b86d0eaa470f92cdaa9f4ed2a961338c49 (commit)
Oops, I hadn't realized this was in `master'. Was it intended? (I
don't remember seeing a discuss
"Michael Gran" writes:
> commit 904a78f11d2d11a58d5df365a44c4fbbd4c96df3
> Author: Michael Gran
> Date: Wed Jul 29 06:38:32 2009 -0700
>
> Add 32-bit characters
>
> This adds the 32-bit standalone characters. Strings are still
> 8-bit. Characters larger than 8-bit can only b
Hello!
I just committed the changes summarized below that add
`-W unused-variable' to "guile-tools compile".
It appears to work well, but only has approximate source location info
for `define-macro' expansions, for instance (but that's another story).
Daniel: could you try it with the Elisp fron
On Jul 30, 2009, at 16:18, Neil Jerram wrote:
The main thing I believe that makes a fluid different from a normal
variable is that a fluid can have a different value in each thread -
which is not relevant to Elisp.
Not yet, at least.
And maybe that's enough. There's other stuff in Emacs besid
On Fri, 2009-07-31 at 00:57 +0200, Ludovic Courtès wrote:
Hello!
>
> "Michael Gran" writes:
>
> > The branch, master has been updated
> >via 77332b21a01fac906ae4707426e00f01e62c0415 (commit)
> > from e5dc27b86d0eaa470f92cdaa9f4ed2a961338c49 (commit)
>
> Oops, I hadn't realized t
Hi Neil,
Neil Jerram wrote:
The only downside I can see to this is that if code were
to be ported from elisp to Scheme there would now be code that assumed a
'() return as false when #f would be false, but this could be fixed
using a predicate like elisp-false? (or null-or-false? or
... somethin
Neil Jerram wrote:
Andy Wingo writes:
Other things needed would be for instance terminating rest-arguments
by %nil rather than '() and the like.
Why is that needed? I.e. Why is it important for a rest argument to
be terminated with %nil instead of with () ?
Well, I don't think it is "impo
Ken Raeburn wrote:
Obviously, it would help a lot to do so. On the other hand, switching
to primitive-ref's would help even more, but I fear we can not easily
do so, because we can not know if a symbol targets a primitive or was
rebound at compile time... BTW, a quick test with Scheme:
[
Hi Neil,
Neil Jerram wrote:
Daniel Kraft writes:
Lambda arguments are still always dynamically bound, which is quite a
pity as it inhibits tail-call optimization;
This prompted me to wonder if using fluids is the best way to
implement dynamic binding.
Perhaps I'm forgetting something basic,
Ken Raeburn wrote:
> And maybe that's enough. There's other stuff in Emacs besides variable
bindings that would require dynamic-wind support, like flet,
save-excursion (preserves current buffer and position),
with-output-to-string and with-output-to-temp-buffer (preserve
'standard-output'), a
16 matches
Mail list logo
