From: Andrew Cagney <ac131313@cygnus.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] Update NEWS for v5.1
Date: Fri, 20 Jul 2001 16:12:00 -0000 [thread overview]
Message-ID: <3B58BACC.1080504@cygnus.com> (raw)
In-Reply-To: <4.2.0.58.20010720130331.01b65f00@ics.u-strasbg.fr>
> About Pascal language addition in NEWS.
>
>
> What about adding this text in front of the missing features ?
>
> * Partial support for debugging Pascal programs.
>
> Support for pascal language is partially included
> Available features are:
> -- Support for pascal specific types like sets.
> -- Automatic recognition of pascal sources based on standard extensions
> -- Pascal like display of types, variables and functions
> -- Pascal expression parser
> However many important features are not yetsupported.
Too negative, you'll never get a job in marketing :-) How about
something like ...
* Support for debugging Pascal programmes.
GDB now includes support for the debugging of Pascal programmes. This
includes the ability to <list of things that do work>.
There are still a few limiations, of note ....
(Contributed by ....)
As to the more general question of ``incomplete support''. This would
be like me demanding test results when someone submits a new port and
then awarding a grade (broken, alpha, beta, incomplete, ...) dependant
on how good/bad they were. No, I'm not going to do that.
Andrew
next prev parent reply other threads:[~2001-07-20 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 9:20 Eli Zaretskii
2001-07-19 10:28 ` Andrew Cagney
2001-07-20 1:52 ` Pierre Muller
2001-07-20 3:50 ` Eli Zaretskii
2001-07-20 4:20 ` Pierre Muller
2001-07-20 7:11 ` Eli Zaretskii
2001-07-20 16:12 ` Andrew Cagney [this message]
[not found] <Pine.SUN.3.91.1010722133856.6415A-100000@is>
2001-07-23 12:39 ` Andrew Cagney
2001-07-25 7:47 ` Eli Zaretskii
2001-07-25 8:12 ` 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=3B58BACC.1080504@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=muller@cerbere.u-strasbg.fr \
/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