I won't get to test it fully until next week, but I replaced the ST usage in 
the C# code with string.Format(), which eliminates the dependency so I can move 
the class back to the runtime. :)

Sam

-----Original Message-----
From: Johannes Luber [mailto:[email protected]] 
Sent: Friday, April 24, 2009 4:52 PM
To: Jim Idle
Cc: [email protected]; Sam Harwell
Subject: Re: [antlr-dev] C# dot spec output

> Johannes Luber wrote:
> > >     I think that it would be trivial to put it back in without a
> string 
> > > 
> template dependency to be honest. I don't have string template in the 
> > > C 
> version for instance. But, whichever way seems best :-)
>       
> >   
> What's your suggestion for doing so? Using object as type?
>   
> Oh, that isn't the problem, Sam was just saying he did not want 
> thatStringTemplate dependency, which the Java runtime has.

Is having a dependency to ST so bad? Or don't you, Sam, want to require ST even 
in the case that one doesn't use it? Is moving the Dot stuff causing an 
organizational problem (extra code not used by ST)? If not, why didn't you, 
Ter, put it there already?

> All you need 
> dois take out the StringTemplate stuff that is being used to generate 
> the.dot spec and replace it with building a String variable instead;

I've been thinking about this today, but I can't think of what you, Jim, would 
put into there. I imagine that the ST version requires merely to fill in the 
blanks. Using merely the data would seem to require an STST equivalent later 
and I don't think you would want that. Putting a stringified ST into the code 
wouldn't make any sense - no way to store the data. So are you directly 
creating Dot output then?

> that's
> what I did in the C version. Otherwise you can almost cut andpaste the
> Java 
> into C# I think.

The "otherwise" refers to decision to leave the ST dependency there?

Johannes
> 
> Jim

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: 
http://www.gmx.net/de/go/multimessenger01
_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org/mailman/listinfo/antlr-dev

Reply via email to