From: Andrew Haley <aph@redhat.com>
To: Sam Ruby <rubys@intertwingly.net>
Cc: Bryce McKinlay <bmckinlay@gmail.com>,
Chris Burdess <dog@bluezoo.org>,
java@gcc.gnu.org
Subject: Re: namespace namespace
Date: Tue, 23 Jun 2009 14:20:00 -0000 [thread overview]
Message-ID: <4A40E497.8090601@redhat.com> (raw)
In-Reply-To: <4A40DBB9.80703@intertwingly.net>
Sam Ruby wrote:
> Andrew Haley wrote:
>> Sam Ruby wrote:
>>> Bryce McKinlay wrote:
>>>> On Tue, Jun 23, 2009 at 10:39 AM, Chris Burdess<dog@bluezoo.org> wrote:
>>>>
>>>>>> Some genius (?) has a namespace called "namespace" :-)
>>>>> That would be Sun. And in Java "namespace" is not a keyword so it's a
>>>>> perfectly legal package name.
>>> namespace also happens to be the name of a concept in XML...
>>>
>>>>>> I think you'll have to edit the header file by hand.
>>> To what? Specifically, what should namespace "namespace" be mapped to?
>>
>> namespace$
>>
>>> It is beginning to appear to me that gcj/g++ will do name mangling of
>>> Java packages without regard to C++ reserved words, resulting in entry
>>> points that can't conveniently be referenced in C++ using CNI.
>>
>> That's right. It should be fairly easy to fix this, though.
>
> Just so that I'm clear: what you are saying is that *both* gcj/g++ and
> gcjh need to be fixed.
If you want to be able to access namespace namespace from CNI, yes.
> I believe that doing such, while necessary, would break the binary
> interface: in particular code which is compiled today to call into JAXP
> would not work with new versions of JAXP that are compiled with a
> version of gcj/g++ which has this fix.
>
> Is that OK?
Yes.
>>> Where can I find the "old" gcjh? The current code is in Java, which
>>> presumably does *not* have the mapping:
>>>
>>> http://cvs.savannah.gnu.org/viewvc/classpath/tools/gnu/classpath/tools/javah/?root=classpath
>>
>> But this is easily fixable, as I pointed out in my previous massage.
>>
>> The old gcjh is very out of date. I'd just fix the current code.
>
> Is that "I'd" or "I'll" :-)
I'd.
> Is there something more I can provide? Will gcj/g++ also be fixed?
Well, I already suggested how you might fix gcjh. It's a matter of
whether you want to be able to access namespace namespace from CNI or
merely not have header files that choke C++. Why not try the fix?
Do you really need CNI access to namespace namespace ?
Andrew.
next prev parent reply other threads:[~2009-06-23 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 2:07 NPE in parser->getDOMImplementation() with CNI Sam Ruby
2009-06-21 15:46 ` Andrew Haley
2009-06-21 20:27 ` Mark Wielaard
2009-06-22 8:20 ` Andrew Haley
2009-06-22 11:13 ` Sam Ruby
2009-06-22 11:08 ` Andrew Haley
2009-06-22 11:33 ` Sam Ruby
2009-06-22 11:51 ` Andrew Haley
2009-06-22 12:33 ` Sam Ruby
2009-06-23 2:09 ` Sam Ruby
2009-06-23 9:30 ` Andrew Haley
2009-06-23 9:40 ` Chris Burdess
2009-06-23 9:58 ` Bryce McKinlay
2009-06-23 10:55 ` namespace namespace (was: NPE in parser->getDOMImplementation() with CNI) Sam Ruby
2009-06-23 12:41 ` namespace namespace Andrew Haley
2009-06-23 13:42 ` Sam Ruby
2009-06-23 14:04 ` Bryce McKinlay
2009-06-23 14:20 ` Andrew Haley [this message]
2009-06-23 20:23 ` Sam Ruby
2009-06-24 9:18 ` Andrew Haley
2009-06-24 11:53 ` Sam Ruby
2009-06-24 12:03 ` Bryce McKinlay
2009-06-24 12:38 ` Andrew Haley
2009-06-23 10:45 ` NPE in parser->getDOMImplementation() with CNI Andrew Haley
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=4A40E497.8090601@redhat.com \
--to=aph@redhat.com \
--cc=bmckinlay@gmail.com \
--cc=dog@bluezoo.org \
--cc=java@gcc.gnu.org \
--cc=rubys@intertwingly.net \
/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).