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: Wed, 24 Jun 2009 09:18:00 -0000 [thread overview]
Message-ID: <4A41EF61.4060902@redhat.com> (raw)
In-Reply-To: <4A4139C1.5060806@intertwingly.net>
Sam Ruby wrote:
> Andrew Haley wrote:
>> Sam Ruby wrote:
>>> 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?
>
> For the moment, I'm doing the equivalent of sed scripts to post process
> the header files (actually, I'm using Ruby -pi -e).
>
> I can certainly fix gcjh locally, but I want to share my results with
> others, and ultimately the fix should go into cvs. I'm certainly
> willing to do my share of the work, but you already identified the
> actual fix. What's the next step?
Someone must apply the change, make a patch, and test the results.
>> Do you really need CNI access to namespace namespace ?
>
> What I am working on is the a Ruby extension that calls out to a HTML 5
> parser that happens to be written in Java and exposes a JAXP interface.
> Along the way, I will have a need to create and access, via CNI,
> objects of the type javax::xml::namespace::QName. I didn't create that
> class, nor can I change it.
>
> http://intertwingly.net/blog/2009/06/23/Validator-Nu-on-GCJ-Update
OK, I see. I was wondering whether this was a theoretical problem that
might just come up or something real. I was also wondering whether this
was relevant to free software.
Given that this looks real, and it is relevant to free software, I can
have a look. However, I can't go back in time, so any change that I make
will not affect the gcj that's in distros for some time to come.
Andrew.
next prev parent reply other threads:[~2009-06-24 9:18 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
2009-06-23 20:23 ` Sam Ruby
2009-06-24 9:18 ` Andrew Haley [this message]
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=4A41EF61.4060902@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).