I haven't touched either of the two current C# targets (CSharp, CSharp2), and the CSharp3 target doesn't derive from that work at all. Also, the CSharp3 target is a work-in-progress until I finish the method naming and properties conventions so it matches the .NET standard patterns. However, the C# ports of the ANTLR Tool and StringTemplate do use the CSharp3 target, so I'd need to keep it in the working branch with those ports. Since the C# port uses the same target codegen templates as the Java version, the internal use of the CSharp3 runtime will not affect any users of any of the other targets.
I'll get you a faxed copy of the agreement to keep on file. Sam -----Original Message----- From: Terence Parr [mailto:[email protected]] Sent: Tuesday, February 17, 2009 2:16 PM To: Sam Harwell Cc: ANTLR-dev Dev; Leon Su; Shaoting Cai Subject: Re: [antlr-dev] ANTLRv3.g On Feb 17, 2009, at 11:07 AM, Sam Harwell wrote: > Prof. Parr: > > I can do that. The other option is adding a branch in your P4 for > the C# > versions of the Tool, StringTemplate, and the WIP CSharp3 target. I > could go back over my revision history and check in all the > incremental > changes with descriptive messages. Would you like to do that > instead? In > particular, I could highlight the revisions that included changes or > bugfixes that aren't present in the latest Java release. Hmm...that would probably require sync with Johannes, current C# guy, to see how he wanted to handle...also I'd need the contrib license signed: http://www.antlr.org/doc/ANTLR-contributor-agreement.pdf Ter _______________________________________________ antlr-dev mailing list [email protected] http://www.antlr.org/mailman/listinfo/antlr-dev
