From: Andrew Haley <aph@redhat.com>
To: Chris Burdess <dog@bluezoo.org>
Cc: Sam Ruby <rubys@intertwingly.net>, java@gcc.gnu.org
Subject: Re: NPE in parser->getDOMImplementation() with CNI
Date: Tue, 23 Jun 2009 10:45:00 -0000 [thread overview]
Message-ID: <4A40B246.5020302@redhat.com> (raw)
In-Reply-To: <9DAA724F-CC05-4A04-8B4D-386238D1D223@bluezoo.org>
Chris Burdess wrote:
> Andrew Haley wrote:
>> Sam Ruby wrote:
>>> Generating a header file for javax::xml::xpath::XPathExpression produces
>>> a file that looks like the following:
>>>
>>> http://git.etherboot.org/scm/people/mcb30/gcc/libjava/javax/xml/xpath/XPathExpression.h
>>>
>>>
>>>
>>> Attempting to include this file produces:
>>>
>>> headers/javax/xml/xpath/XPathExpression.h:16: error: expected identifier
>>> before ‘namespace’
>>> headers/javax/xml/xpath/XPathExpression.h:42: error: expected identifier
>>> before ‘namespace’
>>> headers/javax/xml/xpath/XPathExpression.h:42: error: expected ‘,’ or
>>> ‘...’ before ‘namespace’
>>>
>>> Presumably somebody has encountered this before, and there is an obvious
>>> solution...
>>
>> 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.
>
>> I think you'll have to edit the header file by hand.
>
> Should this not be handled by some automatic munging/unmunging in
> gcjh/gcj? It may prove to be a problem in other places where names are
> not keywords in Java but might be in C/C++/whatever.
Yes, that's right.
gjavah does have code to handle this, but it isn't being called.
Here, in CniPrintStream.java is where the package names are emitted:
// Open new parts.
for (int j = commonIndex; j < pkgParts.length; ++j)
{
indent(out, j + 1);
out.print("namespace ");
out.println(pkgParts[j]);
This line should be
out.println(Keywords.getCxxName(pkgParts[j]));
but there are many places where identifiers are emitted but getCxxName is
not called. This is very odd: for correctness, getCxxName must be called
whenever an identifier is emitted.
Andrew.
prev parent reply other threads:[~2009-06-23 10:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 2:07 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
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 ` Andrew Haley [this message]
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=4A40B246.5020302@redhat.com \
--to=aph@redhat.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).