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
Hey all,
I recently added a global fluid, %file-port-name-canonicalization, which
defaults to #f. But if it's 'absolute, the port name of a file port will
be canonicalized to the absolute path; or, if it's 'relative, the port
name is the canonical name of the file, relative to the %load-path, or
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
() Andy Wingo wi...@pobox.com
() Mon, 19 Apr 2010 16:52:09 +0200
Thoughts?
It sounds complicated.
Does the .go format support the usual ELF-y sections, like
.rodata, .data, etc? Maybe we could just include the source
verbatim in such a section (and avoid mapping it at runtime).
thi
Hi!
Andy Wingo wi...@pobox.com writes:
I recently added a global fluid, %file-port-name-canonicalization, which
defaults to #f. But if it's 'absolute, the port name of a file port will
be canonicalized to the absolute path; or, if it's 'relative, the port
name is the canonical name of the
Hey,
Andy Wingo wi...@pobox.com writes:
Oftentimes you would
want to be able to map a .go file to a corresponding .scm, and currently
it's difficult. For example if you compile in a +build subdirectory of
Guile via `../configure', then the `port-filename' is e.g.
Thien-Thi Nguyen t...@gnuvola.org writes:
() Andy Wingo wi...@pobox.com
() Mon, 19 Apr 2010 16:52:09 +0200
Thoughts?
It sounds complicated.
Does the .go format support the usual ELF-y sections, like
.rodata, .data, etc? Maybe we could just include the source
verbatim in such a
