unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Guile 2.2 TODO
Date: Sat, 14 Sep 2013 15:48:45 +0200	[thread overview]
Message-ID: <87d2obo6o2.fsf@gnu.org> (raw)
In-Reply-To: 87vc2kztv1.fsf@pobox.com

Hi,

Thanks for the road map!

Andy Wingo <wingo@pobox.com> skribis:

>   - Add machinery to (system vm debug) to get a DIE for a procedure, if
>     it is present.

It would be great if it would support .gnu_debuglink too (info "(gdb)
Separate Debug Files").

Another thing I noticed is that in 2.0 we have location info for code,
but not for (global) variable definitions in general (which prevents
M-. from doing anything useful for non-procedure top-level variables.)

How would that work with DWARF?

> I think that's pretty much it.  Obviously it would be nice to get a lot
> of other things into 2.2 but this is the necessary bit.  I think we
> should shoot for a 2.1.0 release around 1 December; dunno.

Sounds like a good plan.

Personally I’m still very much on the Guix (dark?) side of things, but
I’d like to get on the 2.1 train sometime in the coming months.

Ludo’.




  parent reply	other threads:[~2013-09-14 13:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-01 11:03 Guile 2.2 TODO Andy Wingo
2013-09-01 19:07 ` Peter TB Brett
2013-09-02 20:01   ` Andy Wingo
2013-09-14 13:48 ` Ludovic Courtès [this message]
2013-09-17 20:16   ` Andy Wingo
2013-10-03 21:27 ` Andy Wingo
2013-10-18  9:56 ` Andy Wingo
2013-10-29 12:27   ` Ludovic Courtès

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=87d2obo6o2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).