[Swift-devel] changes

[Tim Armstrong]

Trying to run a java parser from the C client sounds like an additional
source of deployment/configuration hassles.  Is there a particular reason
why it needs to be the client though rather than the Coaster service that
handles the configuration?

To me it would make the most sense to either choose a simple constrained
format that its feasible to write a custom parser for, or to just use JSON
or XML where there are lots of existing parsers.

- Tim


On Sat, Jul 5, 2014 at 1:03 PM, Mihael Hategan <hategan at mcs.anl.gov> 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/fad357d3/attachment.html>