public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: "Anthony Green" <green@redhat.com>
To: <apbianco@cygnus.com>
Cc: <rhug-rhats@sources.redhat.com>
Subject: Re: xalan + javascript extension working
Date: Wed, 10 Oct 2001 11:59:00 -0000	[thread overview]
Message-ID: <000f01c151be$709da420$4ce7b4cd@cygnus.com> (raw)
In-Reply-To: <15300.35197.936819.986407@fencer.cygnus.com>

Alex wrote:
> It comes with its own snapshot of apache.oro.text.regex which
> differs from the one imported in rhug, though they might be merge-able
> (the diff is 79K.)

It's interesting that most of these bigger programs come with their own .jar
files of shared infrastructure (regexp stuff, xerces even).  Rather than rely
on the bundled jar files, I've chosen to integrate the original library distro
as a top-level package, which is why rhug contains java_cup and bcel (used by
xerces).  We should try to use the existing org.apache.oro if at all possible.

> jython might have to be modified as (as I understand it) spits out
> class files that we would prefer to compile.

My guess is that it works more like rhino and xalan, in that it produces
in-memory class definitions which it simply interprets, but can also produce
class files if you prefer to use them that way.  If this is the case then we
don't have to make any changes.

> I can give it a try if you want. I've been looking forward to running
> jython as it would provide us with an excellent opportunity to run
> loads non regression tests.

That would be cool.

AG


      reply	other threads:[~2001-10-10 11:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-07 16:58 Anthony Green
2001-10-10 10:46 ` Alexandre Petit-Bianco
2001-10-10 11:59   ` Anthony Green [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='000f01c151be$709da420$4ce7b4cd@cygnus.com' \
    --to=green@redhat.com \
    --cc=apbianco@cygnus.com \
    --cc=rhug-rhats@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).