Hi Stefan,
On Fri 16 Apr 2010 19:47, stefan stefan.ta...@spray.se writes:
I learned to like to trace functions when
debugging and found out that guiles version needs work.
so has anybody steped up to fix this?
It's possible to trace the execution of a whole tree of functions:
Greets,
On Sat 17 Apr 2010 01:15, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
So, my thought is to extend procedures with an additional pointer, a
pointer to a native code structure.
(So your point is what should we do now to allow for such experiments
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
Hi,
Andy Wingo wi...@pobox.com writes:
It's a shame that GCC has not been able to support LLVM's level of
innovation,
I don’t think innovation is the problem (did you read the 4.5 release
notes?). However, it’s been too much of a monolithic compiler, unlike
LLVM, although plug-ins will now
Good stuff, Andy!
On Apr 16, 2010, at 07:09, Andy Wingo wrote:
Currently, Guile has a compiler to a custom virtual machine, and the
associated toolchain: assemblers and disassemblers, stack walkers, the
debugger, etc. One can get the source location of a particular
instruction pointer, for
