2008/11/23 Clinton Ebadi <[EMAIL PROTECTED]>:
> "Linas Vepstas" <[EMAIL PROTECTED]> writes:
>
>> Hi,
>>
>> 2008/11/23 Neil Jerram <[EMAIL PROTECTED]>:
>>> If we had a clearer statement of
>>> the present, it would not matter so much how people describe the past.
>>
>> Is there a clear expression o
"Linas Vepstas" <[EMAIL PROTECTED]> writes:
> Hi,
>
> 2008/11/23 Neil Jerram <[EMAIL PROTECTED]>:
>> If we had a clearer statement of
>> the present, it would not matter so much how people describe the past.
>
> Is there a clear expression of a vision for the future?
> What might one look forward
2008/11/23 Ludovic Courtès <[EMAIL PROTECTED]>:
>
> Exactly, thanks! Now, I was actually using SRFI-34's
> `with-exception-handler', which I expected to behave like
> `with-throw-handler'. Should we change `with-exception-handler' to use
> `with-throw-handler' instead of `lazy-catch'?
Yes, I thi
Hi Neil,
"Neil Jerram" <[EMAIL PROTECTED]> writes:
> This is as expected. Note that there is nothing like dynamic-wind
> inside fluid-set! Did you perhaps mean with-fluids instead? If you
> used with-fluids, I would expect the same behaviour as you've
> described for parameterize.
Yes, that c
2008/11/23 Ludovic Courtès <[EMAIL PROTECTED]>:
> Hello Guilers!
>
> I noticed the following subtle difference between fluids and SRFI-39
> parameters when accessed from a `lazy-catch' handler:
>
> (define fl (make-fluid))
> (fluid-set! fl 'outside)
>
> (lazy-catch #t
> (lambda ()
>
Hello Guilers!
I noticed the following subtle difference between fluids and SRFI-39
parameters when accessed from a `lazy-catch' handler:
(define fl (make-fluid))
(fluid-set! fl 'outside)
(lazy-catch #t
(lambda ()
(fluid-set! fl 'inside)
(throw
Hi,
2008/11/23 Neil Jerram <[EMAIL PROTECTED]>:
> If we had a clearer statement of
> the present, it would not matter so much how people describe the past.
Is there a clear expression of a vision for the future?
What might one look forward to? What needs to be
done?
--linas
Hey Neil,
On Sun 23 Nov 2008 10:40, "Neil Jerram" <[EMAIL PROTECTED]> writes:
> OK, understood. I guess we should have it then. But the problem is
> that - as Andy has said in his response - so many people know Guile
> mainly as "the project that RMS started because of the Tcl war", and I
> don
Hi,
Sebastian Tennant <[EMAIL PROTECTED]> writes:
> I very much doubt it's possible, but is there any way of getting Guile
> to include a timestamp in it's error reporting?
>
> For example:
>
> guile> foo
> 2008-11-20 23:17:11 ERROR: Unbound variable: foo
> 2008-11-20 23:17:11 ABORT: (unbound-
Hello,
Keith Wright <[EMAIL PROTECTED]> writes:
> Several other directions seem to have been pursued for
> a while and then abandonded. If nobody remembers why,
> then maybe someone will try the same thing again.
> Maybe that's a good thing, because a worthy goal
> remains to be accomplished. I
2008/11/21 Sebastian Tennant <[EMAIL PROTECTED]>:
> Hi all,
>
> I very much doubt it's possible, but is there any way of getting Guile
> to include a timestamp in it's error reporting?
>
> For example:
>
> guile> foo
> 2008-11-20 23:17:11 ERROR: Unbound variable: foo
> 2008-11-20 23:17:11 ABORT:
2008/11/22 Keith Wright <[EMAIL PROTECTED]>:
>
> It can't hurt, can it?
That is rarely a good enough argument.
> What _would_ help us?
A better statement of Guile's current purpose.
> Whatever happened to tcl?
Are you joking here? If not, see gitk.
> Those who do not remember history are doo
2008/11/21 Andy Wingo <[EMAIL PROTECTED]>:
>
> I think that the problem that history addresses is the definition of
> Guile -- that is, who and what we are.
Hi Andy,
Following on from my response to Seb... I think this is the key
point, the definition of Guile today. If, from this work, we can
2008/11/21 Sebastian Tennant <[EMAIL PROTECTED]>:
>
> It will help different people in different ways and no doubt there are
> some, like yourself, whom it won't help at all.
>
> Personally, I appreciate histories most when I'm new to a subject (for
> obvious reasons) but a good history makes inter
14 matches
Mail list logo
