From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: 5.1 NEWS
Date: Sun, 08 Jul 2001 19:43:00 -0000 [thread overview]
Message-ID: <3B491A68.8010801@cygnus.com> (raw)
In-Reply-To: <87u20owqvw.fsf@cgsoftware.com>
Hmm, how can I put this.
GDB's Pascal support is new, people will have reasonable expectations
and a keenness to help fix it. GDB's C++ support, on the other hand, is
old. Unless told otherwize, people are going to assume that it all
works perfectly, even for the new v3 C++ ABI.
In using the word ``limited'', I'm trying to set expecations. If you
think there is a better turn of phrase then please put it forward.
Andrew
> Andrew Cagney <ac131313@cygnus.com> writes:
>
>
>> Hello,
>>
>> The NEWS file could do with a few more updates.
>>
>> Pascal and ``limited support for the C++ v3.0 ABI'' come to mind.
>
>
> Pascal support doesn't work all that well.
> For starters, it doesn't even set the case sensitivity to off in the language
> definition, for instance. Forget about actually doing good pascal debugging.
> I noticed it barely works when I started verifying i did the right
> thing for fortran and pascal in the new typesystem.
> So if you put something about pascal, put "limited pascal support".
next prev parent reply other threads:[~2001-07-08 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 10:23 Andrew Cagney
2001-07-07 11:11 ` Daniel Berlin
2001-07-08 1:18 ` Eli Zaretskii
2001-07-08 19:43 ` Andrew Cagney [this message]
2001-07-08 22:06 ` Daniel Berlin
2001-07-09 0:03 ` Eli Zaretskii
2001-07-09 0:53 ` Daniel Berlin
2001-07-09 1:31 ` Eli Zaretskii
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=3B491A68.8010801@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dan@cgsoftware.com \
--cc=gdb@sources.redhat.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