From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: TODO for 2.0
Date: Mon, 19 Apr 2010 11:33:54 +0200 [thread overview]
Message-ID: <m3d3xvbxbx.fsf@pobox.com> (raw)
In-Reply-To: <87tyr8zdlo.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 18 Apr 2010 22:53:55 +0200")
Hi,
On Sun 18 Apr 2010 22:53, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@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 embed 'documentation symbol in meta-procedure
>
> Likewise: review bytecodes; for instance, most of time integers are
> written in native endianness, but sometimes they are in big endian, and
> sometimes the width of integers seems quite arbitrary.
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 these; and I'd like an
opportunity to comment on patches :-)
> There’s also a wealth of optional things on my to-do list, of course.
> ;-)
Hehe, indeed.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-04-19 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 11:59 TODO for 2.0 Andy Wingo
2010-04-17 18:30 ` Mike Gran
2010-04-18 15:57 ` Julian Graham
2010-04-19 9:12 ` Andy Wingo
2010-04-19 12:11 ` Julian Graham
2010-04-18 20:53 ` Ludovic Courtès
2010-04-19 9:33 ` Andy Wingo [this message]
2010-04-19 17:09 ` Ken Raeburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d3xvbxbx.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).