Hi Stefan,
Stefan Israelsson Tampe stefan.ita...@gmail.com writes:
I wouldl like to start a discussion of introducing a way to mark
variables as special, and by that mean that set! variables does not
nessesary get boxed.
I don't think you fully understand the ramifications of what you're
On Thu 21 Mar 2013 01:38, Mark H Weaver m...@netris.org writes:
Chris K. Jester-Young has been hard at work getting his SRFI-41
implementation ready in time for Guile 2.0.8, and I think it might be
ready to push. What do you think?
Needs documentation.
--
http://wingolog.org/
Ok, This was a first step to get what I would like to have implemented
in the tree il backend (Not for scheme but perhaps something useful
for e.g. emacs-lisp, python etc).
My main issue with the current setup is that adding undoing and
redoing feature with the help of prompts will fail in 95% of
Hi Mark,
Mark H Weaver m...@netris.org skribis:
l...@gnu.org (Ludovic Courtès) writes:
I plan to commit the patch below, which adds bindings for ‘sendfile’.
Comments?
Looks great to me, modulo one comment below.
Thanks for the quick review!
I especially like the fact that although it
On Fri 15 Mar 2013 22:01, Brent Pinkney b...@4dst.com writes:
When I resume the continuation in another thread, all works perfectly
UNLESS the continued execution throws and exception.
Then guile exits with a core dump.
By contrast if I resume the continuation in the same thread and then
On Thu 21 Mar 2013 10:40, l...@gnu.org (Ludovic Courtès) writes:
l...@gnu.org (Ludovic Courtès) writes:
I plan to commit the patch below, which adds bindings for
‘sendfile’.
Should probably go in gnulib at some point, no? Looks good tho :)
--
http://wingolog.org/
On 03/21/13 11:15, Ludovic Courtès wrote:
Noah Lavine noah.b.lav...@gmail.com skribis:
I've thought for a while that if I had time (which I know I won't) I would
make a module called (linux) with bindings for non-POSIX Linux kernel
features. What do you think of this idea? If so, what do you
Andy Wingo wi...@pobox.com skribis:
On Thu 21 Mar 2013 10:40, l...@gnu.org (Ludovic Courtès) writes:
l...@gnu.org (Ludovic Courtès) writes:
I plan to commit the patch below, which adds bindings for
‘sendfile’.
Should probably go in gnulib at some point, no?
Yes, you’re right. I’ll see
On 03/21/13 11:43, Andy Wingo wrote:
On Fri 15 Mar 2013 22:01, Brent Pinkney b...@4dst.com writes:
When I resume the continuation in another thread, all works perfectly
UNLESS the continued execution throws and exception.
Then guile exits with a core dump.
By contrast if I resume the
On Thu 21 Mar 2013 14:53, Andrew Gaylard a...@computer.org writes:
(catch #t
(λ ()
(throw 'oops)) ; should not crash the vm
(λ ()
(display Success!)(newline))) ; never reached
the VM still cores; Success is never shown. However, you've probably
spotted my mistake: the handler should be (λ
Hello,
Yes, you're completely right - making it work on all platforms is much
better than what I had proposed. I'm glad you're doing this.
Thanks,
Noah
On Thu, Mar 21, 2013 at 5:15 AM, Ludovic Courtès l...@gnu.org wrote:
Hi Noah,
Noah Lavine noah.b.lav...@gmail.com skribis:
I've thought
On Thursday, March 21, 2013 11:35:19 AM Noah Lavine wrote:
(lambda ()
(let ((x 5))
(set! x (compute-1 x))
(set! x (compute-2 x))
x))
becomes
(lambda ()
(let ((k1 (lambda (x) (k2 (compute-2 x
(k2 (lambda (x) x)))
(k1 (compute-1 x
However, this
l...@gnu.org (Ludovic Courtès) skribis:
Alternately, would you suggest using a different approach?
Attached is a patch to use Guile’s Texinfo support [0] to build said
file. Guile’s Texinfo parser is incomplete but sufficient to handle
those docstrings.
It solves an actual bug for anyone
Hi Ludo
Attached is a patch to use Guile’s Texinfo support [0] to build said
file. Guile’s Texinfo parser is incomplete but sufficient to handle
those docstrings.
OK to commit?
If Guile depends on Guile for multiple stages the build, it becomes
difficult to recover from a problem when
Stefan, you're still describing your proposal in terms of low-level
implementation details such as stacks. In the general case, we cannot
store environment structures on the stack. Furthermore, in the general
case *all* variables in scheme are bound to locations, not values. Only
in special
On Thursday, March 21, 2013 03:03:06 PM Mark H Weaver wrote:
Stefan, you're still describing your proposal in terms of low-level
implementation details such as stacks. In the general case, we cannot
store environment structures on the stack. Furthermore, in the
general case *all* variables
Mike Gran spk...@yahoo.com skribis:
Attached is a patch to use Guile’s Texinfo support [0] to build said
file. Guile’s Texinfo parser is incomplete but sufficient to handle
those docstrings.
OK to commit?
If Guile depends on Guile for multiple stages the build, it becomes
difficult to
Hi,
Stefan and Mark, I think you are talking past each other. Stefan is
offering a very concrete definition of what he wants, and Mark is looking
for a more abstract version. Here is what I think Stefan wants, in the
language of R5RS' storage model:
A variable is simply a name for a particular
Guileôòùs Texinfo parser
Argh. The idea of a full second Texinfo parser in GNU is fundamentally
wrong. If you want to call it a Guile docstring parser, whose language
happens to bear some resemblance to a subset of Texinfo, fine.
Anyway, your change to use more Guile in the Guile build
19 matches
Mail list logo
