Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dan@cgsoftware.com>
To: Per Bothner <per@bothner.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: obvious set_cu_language patch
Date: Fri, 08 Jun 2001 13:51:00 -0000	[thread overview]
Message-ID: <87vgm6snjf.fsf@cgsoftware.com> (raw)
In-Reply-To: <m2pucevgf6.fsf@kelso.bothner.com>

Per Bothner <per@bothner.com> writes:

> Andrew Cagney <ac131313@cygnus.com> writes:
> 
>> Per, can you add your self to the MAINTAINERS file as write after approval.
> 
> Actually, I was thinking of this instead.  Is this ok?

I'd pay you money to do it.
:)

While i'm redoing the type system, I was just about to ask a java
person the following:
in jv-lang.c, in java_array_type, it says "FIXME: This is bogus! Java
arrays are not gdb arrays!".

Could you please point me to where i can find out what java arrays
*are*, so i can make a type structure for them (the new typesystem is
a hierarchy of structs, rather than a single type struct.  This means
whatever java arrays *are*, can easily be represented and handled,
with no fuss or muss).

> 
> Index: MAINTAINERS
> ===================================================================
> RCS file: /cvs/src/src/gdb/MAINTAINERS,v
> retrieving revision 1.93
> diff -u -r1.93 MAINTAINERS
> --- MAINTAINERS	2001/05/10 21:10:09	1.93
>+++ MAINTAINERS	2001/06/08 20:21:15
> @@ -245,6 +245,7 @@
>  language support	David Taylor		taylor@cygnus.com
>    C++ support		Daniel Berlin		dan@cgsoftware.com
>    Java support		Anthony Green 		green@cygnus.com
>+			Per Bothner		per@bothner.com
>    Objective-C/C++	Klee Dienes		kdienes@apple.com
>  			Jim Ingham		jimgham@apple.com
>    Pascal support	Pierre Muller		muller@sourceware.cygnus.com
> 
> -- 
> 	--Per Bothner
> per@bothner.com   http://www.bothner.com/per/

-- 
"I'd like to sing you a song now about my old girlfriend.  It's
called, "They'll Find Her When the Leaves Blow Away 'Cause I'm
Not Raking 'Til Spring."
"-Steven Wright


  parent reply	other threads:[~2001-06-08 13:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 23:22 Per Bothner
2001-06-07 23:50 ` Daniel Berlin
2001-06-08 11:01   ` Per Bothner
2001-06-08 14:04     ` Stan Shebs
2001-06-08 14:34       ` Daniel Berlin
2001-06-08 13:04 ` Andrew Cagney
     [not found]   ` <m2pucevgf6.fsf@kelso.bothner.com>
2001-06-08 13:51     ` Daniel Berlin [this message]
     [not found]       ` <8766e6eke4.fsf@creche.redhat.com>
2001-06-08 14:23         ` Per Bothner
     [not found]       ` <npelsq28sh.fsf_-_@zwingli.cygnus.com>
2001-06-11 11:43         ` Rewriting the type system Daniel Berlin
2001-06-11 16:58           ` Stan Shebs
2001-06-12  1:44           ` Eli Zaretskii
2001-06-12  9:12             ` Daniel Berlin
2001-06-12 10:01               ` Eli Zaretskii
2001-06-12 10:16           ` Jim Blandy
2001-06-12 10:44             ` Daniel Berlin
2001-06-12 14:02               ` Stan Shebs
2001-06-13  1:45                 ` Eli Zaretskii
2001-06-12 11:08             ` Daniel Berlin
2001-06-12 14:03           ` Andrew Cagney
2001-06-12 21:37             ` Daniel Berlin
2001-06-25 14:13 ` obvious set_cu_language patch Elena Zannoni

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=87vgm6snjf.fsf@cgsoftware.com \
    --to=dan@cgsoftware.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --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