The main drivers we talked about ages ago (can't find it now) were:
- Decoupling the syntax tree from the interpretation, so that
alternate interpreters/compilers can be easily plugged in.
- Allow the grammar to change without the need to keep changing the
generated code.
- Structure the interpret
On Oct 21, 2007, at 4:23 PM, [EMAIL PROTECTED] wrote:
2.0 starting
ooh!
what all do you want to achieve?
-pete
--
[EMAIL PROTECTED] - http://fotap.org/~osi
smime.p7s
Description: S/MIME cryptographic signature
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
Th
Hi,
(this may be a stupid question, but I did not follow the setup of
Continuum too closely)
where are the results of CI stored? Obviously not at the location, to
which the link for the nightly builds on our main page points to
(http://people.apache.org/builds/commons/nightly/). Here only outdate
The apachecon logo isn't showing on commons.apache.org. Thought I'd mention it.
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi!
Maybe it would make more sense to do these changes in commons-jci-fam
first and then move that to a new commons-fam?
Sounds reasonable, although I still think IO is a better home for fam
than a separate component.
In any case, it would be creat if the code is built in a way that makes
