-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/2010 11:51 PM, David Ashley wrote:
All -
I started today by merging the incubator/nixclib into the main trunk. I
want to continue this process to include the following:
incubator/hostemu
incubator/orxcurses (for *nix only at this
I'm very happy to see CSVStream merge into trunk.
I get the impression that it is being used in a few places out there and is
stable.
Jon
On 22 April 2010 22:51, David Ashley david.ashley@gmail.com wrote:
All -
I started today by merging the incubator/nixclib into the main trunk. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm currently trying to write a grammar for ooRexx to build a workbench
on it. However, I face some problems.
The grammar requires to be context free, and have no left recursions.
Internally, it will use ANTLR to do the parsing, which is a
Take a look at incubator/orxutils/ocube. The ocube program contains a
parser written in ooRexx to parse the grammar for the implementation of
ocube. The grammer for ocube is a simplified version of the Rexx grammer
so you might be able to use it as a base for your work. The code was
written
I seem to remember that the ANSI standard has (classic) Rexx in BNF.
You can get a PDF here:
http://www.rexxla.org/rexxlang/standards/j18pub.pdf
Moritz Hoffmann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm currently trying to write a grammar for ooRexx to build a
Is ooRexx context free? It seems to be that it isn't, but I could be
wrong. Very thin in knowledge in this area.
Bruce
On Apr 23, 2010, at 10:35 AM, Gil Barmwater wrote:
I seem to remember that the ANSI standard has (classic) Rexx in BNF.
You can get a PDF here:
Having spent some time reading parts of the code now, I have made some
modifications which I will send to Rick for possible inclusion. One was
a bug I believe and I changed the option attributes, e.g. multilines,
to use the ::attribute vs ::method ... attribute for consistency.
Mainly,
On Fri, Apr 23, 2010 at 11:24 AM, Gil Barmwater gbarmwa...@alum.rpi.edu wrote:
Having spent some time reading parts of the code now, I have made some
modifications which I will send to Rick for possible inclusion. One was
a bug I believe and I changed the option attributes, e.g. multilines,
I think submitting a patch would be a good idea too. Gil is sending
these in patch form any way, so the merge is no more difficult for me
to handle.
Rick
On Fri, Apr 23, 2010 at 2:47 PM, Mark Miesfeld miesf...@gmail.com wrote:
On Fri, Apr 23, 2010 at 11:24 AM, Gil Barmwater
Not sure what you mean by ...is it possible for you to submit a
patch...; I've been generating a patch file and just forwarding it to
Rick. How else would I do it w/o opening a tracker item and attaching
the patch file to it? Or is that what you are suggesting?
Mark Miesfeld wrote:
On Fri,
We have a tracker system just for submitted patches:
https://sourceforge.net/tracker/?group_id=119701atid=684732
Rick
On Fri, Apr 23, 2010 at 3:50 PM, Gil Barmwater gbarmwa...@alum.rpi.edu wrote:
Not sure what you mean by ...is it possible for you to submit a
patch...; I've been generating a
Sorry, wasn't aware of that one :-( I'll use it in the future and just
post questions or comments here. Thanks!
Rick McGuire wrote:
We have a tracker system just for submitted patches:
https://sourceforge.net/tracker/?group_id=119701atid=684732
Rick
On Fri, Apr 23, 2010 at 3:50 PM,
12 matches
Mail list logo
