[Swift-devel] New parsing tool for swift.properties

[Tim Armstrong]

I already replied to the other email but I'd strongly argue for a solution
that avoids imposing any additional steps, intermediate files, or
dependencies in running a Swift/T program.  It's difficult enough to
compile and run a Swift/T application already.


On Sat, Jul 5, 2014 at 1:20 PM, Mihael Hategan <hategan at mcs.anl.gov> wrote:

> Maybe. I have no idea how the /K configuration structure makes sense
> in /T. Tim, Justin?
>
> Mihael
>
> On Sat, 2014-07-05 at 13:11 -0500, Michael Wilde wrote:
> > was: Re: [Swift-devel] changes
> >
> > I think this tool (Typesafe config) looks promising; I would try it.
> >
> > Once you have a property parser in Swift/K, that can be readily turned
> > into a standalone Java command to run for Swift/T, if/when needed, which
> > can emit Tcl or whatever other flat propoerty format is needed.
> >
> > Sound reasonable?
> >
> > - Mike
> >
> >
> > On 7/5/14, 1:03 PM, Mihael Hategan wrote:
> > > On Sat, 2014-07-05 at 09:34 -0500, Michael Wilde wrote:
> > >> This looks very good, deals with a lot of parsing issues, and is
> > >> licensed under Apache 2 (same as Swift).
> > >>
> > >> But is it Java-only?   If so, then down the road, for Swift/T with
> > >> Coaster C client, just parse options using a Java app perhaps?
> > > It's Java only. I don't know. I guess writing one parser is better than
> > > writing two parsers.
> > >
> > > The only other reasonable choice is XML unless somebody knows something
> > > else.
> > >
> > > Mihael
> > >
> > >
> >
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140705/d98ab1b8/attachment.html>