Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aidan Skinner <aidan@velvet.net>
To: Hilfinger@otisco.mckusick.com
Cc: jimb@redhat.com, ac131313@redhat.com, aidan@velvet.net,
	drow@mvista.com, per@bothner.com, green@redhat.com,
	muller@cerbere.u-.strasbg.fr, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add type support for Ada
Date: Mon, 30 Sep 2002 20:17:00 -0000	[thread overview]
Message-ID: <20021001041712.E8933@velvet.net> (raw)
In-Reply-To: <200209280925.CAA10025@otisco.McKusick.COM>; from hilfingr@otisco.mckusick.com on Sat, Sep 28, 2002 at 02:25:59AM -0700

[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

On Sat, Sep 28, 2002 at 02:25:59AM -0700, Paul N. Hilfinger wrote

Thanks for answering these Paul. :)

> > It looks to me as if the string cleanup stuff is distinct from the
> > fixed instance stuff.  These should be submitted as separate patches.
> 
> They definitely are logically separate changes.

Yeah, I'll split and resubmit and probably take the opportunity to
include some more string cleanup stuff, rather than just the bits that
ada-* reference...

> > Should base_type use the tortoise-and-hare algorithm to detect cycles?
> 
> An interesting suggestion.  However, there is at least one existing
> place where GDB doesn't bother.  Compare with the following (non-Ada-

I think it's worthwhile doing here, and if it works nicely it can be
stolen for other places. My next revision of this patch will include
this.

> Umm. Interesting questions.  As I recall, I had the impression that 
> a self-referencing range type COULD occur legitimately, but given that was

I think they can, but my current understanding of the gdb type system
probably bears some resemblence to swiss cheese. ;)

I'll experiment a bit with trying to create one and see what I can find.

> 4 years ago, my memory could be faulty.  I suspect these tests were simply
> bullet-(or segfault)-proofing.  Replacing the NULL check at least with
> an error would probably be a worthy experiment.

Sounds like a plan.

- Aidan

-- 
aidan@velvet.net  http://www.velvet.net/~aidan/  aim:aidans42
http://www.livejournal.com/users/aidan_skinner/
finger for pgp key: 01AA 1594 2DB0 09E3 B850  C2D0 9A2C 4CC9 3EC4 75E1

[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

  reply	other threads:[~2002-10-01  3:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 20:00 Aidan Skinner
2002-09-26 19:24 ` Andrew Cagney
2002-09-27 13:08   ` Jim Blandy
2002-09-28  2:24     ` Paul N. Hilfinger
2002-09-30 20:17       ` Aidan Skinner [this message]
2002-10-02 11:59         ` Jim Blandy
2002-10-02 11:57       ` Jim Blandy

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021001041712.E8933@velvet.net \
    --to=aidan@velvet.net \
    --cc=Hilfinger@otisco.mckusick.com \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=green@redhat.com \
    --cc=jimb@redhat.com \
    --cc=muller@cerbere.u-.strasbg.fr \
    --cc=per@bothner.com \
    /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