Rob Browning <[EMAIL PROTECTED]> writes:
> Not as far as I'm concerned, though would a trivial NEWS entry be
> appropriate? i.e. perhaps something like
>
> ** make-stack can now correctly construct a stack from a continuation.
>
> if that's correct.
Yes, that would be fine.
Neil
__
Neil Jerram <[EMAIL PROTECTED]> writes:
> Yes, for `(call/cc make-stack)'. make-stack is supposed to be able to
> construct a stack from a continuation, a debug object, or from `#t',
> which means the current evaluation stack. But the make-stack code was
> missing a lot of the relocations that a
Kevin Ryde <[EMAIL PROTECTED]> writes:
> Neil Jerram <[EMAIL PROTECTED]> writes:
>>
>> Thanks. In this case, I'm pretty sure my bug fixes don't qualify as
>> NEWS.
>
> What is the continuations versus stack bit you added some tests for?
> Is it a fix for something?
Yes, for `(call/cc make-stack)
Kevin Ryde <[EMAIL PROTECTED]> writes:
> I find the way 1.6.7 is said first here pretty unclear. I know it's
> been that way for a long time, but I always have to think for which
> version I'm reading about.
I agree. I thought the same thing myself today, but went ahead and
stuck with the conve
Kevin Ryde <[EMAIL PROTECTED]> writes:
> Rob Browning <[EMAIL PROTECTED]> writes:
>>
>> cvs -qz5 diff -u -r release_1-6-7
>
> I added the bits I did, mostly fixes from bug reports. I've tried to
> keep it brief, none are too terrible, unless you actually wanted to
> use something affected :).
Rob Browning <[EMAIL PROTECTED]> writes:
>
> Changes since Guile 1.6.7 (changes in 1.6.8):
I find the way 1.6.7 is said first here pretty unclear. I know it's
been that way for a long time, but I always have to think for which
version I'm reading about. Maybe just,
Guile 1.6.8 changes
Rob Browning <[EMAIL PROTECTED]> writes:
>
> cvs -qz5 diff -u -r release_1-6-7
I added the bits I did, mostly fixes from bug reports. I've tried to
keep it brief, none are too terrible, unless you actually wanted to
use something affected :).
___
Gu
Neil Jerram <[EMAIL PROTECTED]> writes:
>
> Thanks. In this case, I'm pretty sure my bug fixes don't qualify as
> NEWS.
What is the continuations versus stack bit you added some tests for?
Is it a fix for something?
___
Guile-devel mailing list
Guile-
Rob Browning <[EMAIL PROTECTED]> writes:
> The general rule I've heard is that NEWS should include "user visible
> changes", but of course that leaves a lot of room for discretion.
>
> I suppose I'd say that it depends on the bug fix. If a bug was fixed
> that people might have noticed and were h
Rob Browning <[EMAIL PROTECTED]> writes:
> If you have time, could those of you who have committed changes to 1.6
> (since 1.6.7) check out a current 1.6 tree, look over the output of
>
> cvs -qz5 diff -u -r release_1-6-7
>
> and make sure that all of your changes have appropriate NEWS entries?
Neil Jerram <[EMAIL PROTECTED]> writes:
> There are two bug fixes by me, but I don't think they merit NEWS
> entries. (Bug fixes don't normally, do they?)
The general rule I've heard is that NEWS should include "user visible
changes", but of course that leaves a lot of room for discretion.
I su
Rob Browning <[EMAIL PROTECTED]> writes:
> If you have time, could those of you who have committed changes to 1.6
> (since 1.6.7) check out a current 1.6 tree, look over the output of
>
> cvs -qz5 diff -u -r release_1-6-7
>
> and make sure that all of your changes have appropriate NEWS entries?
12 matches
Mail list logo
