Hi Julian,
On Sun 18 Apr 2010 17:57, Julian Graham jool...@gmail.com writes:
Unbound variable errors during `make' but not when compiling from
the REPL.
[0] - http://www.mail-archive.com/guile-devel@gnu.org/msg05278.html
I'll add this to my list, then. Is there no smaller test case than
Hi,
On Sun 18 Apr 2010 22:53, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
* some bytecode tweaks
- function prologues can be shorter in the common case
- perhaps docstrings should take less space in objcode, by allowing
them to be specified
Hi Andy,
I'll add this to my list, then. Is there no smaller test case than
compiling the entire wrapper module? Does this problem occur with
smaller libraries as well? I would love to have a simple test case that
I can run on master. I'll spelunk on your branch, though, if that's
On Apr 19, 2010, at 05:33, Andy Wingo wrote:
Dunno. To be able to write in native endianness and actually see
benefits, the data needs to be aligned, too. Integer widths are
generally chosen as some point in the size/speed vs generality tradeoff.
I would be very hesitant about poking some of
Hi Andy,
Please feel free to reply with your own lists. Please reply only with
things that you feel must be dealt with before 2.0, by somebody, or
things that you personally plan to work on (blocker or not).
Unless R6RS-lib is something that can be merged in a subsequent 2.0.x
stable
Hi Andy,
Andy Wingo wi...@pobox.com writes:
* some bytecode tweaks
- function prologues can be shorter in the common case
- perhaps docstrings should take less space in objcode, by allowing
them to be specified positionally in the program metadata,
removing need to
Hi all,
I would like to share my personal list of things to do before 2.0.
* some bytecode tweaks
- function prologues can be shorter in the common case
- perhaps docstrings should take less space in objcode, by allowing
them to be specified positionally in the program
Hi Andy,
From: Andy Wingo wi...@pobox.com
Please reply only with things that you feel must
be dealt with before 2.0, by somebody, or
things that you personally plan to work on (blocker or
not).
Reenable Turkish casing tests in i18n.test.
Check for a BOM if the encoding is UTF-16 or
