[wg-camlp4] Meta Programming from the view of the implementaion
Hongbo Zhang
hongboz at seas.upenn.edu
Thu Jan 31 13:46:35 GMT 2013
On Thu, Jan 31, 2013 at 8:43 AM, Török Edwin <edwin+ml-ocaml at etorok.net>wrote:
> On 01/31/2013 03:27 PM, Hongbo Zhang wrote:
> >
> >
> > > In Fan,
> > > {:json| ... |}
> > > if "|}" is used inside,*the user (optionally) can introduce a new
> separator following "|" immediately*
> > > {:json|/ ... /|}
> >
> > So this would be similar to Leo's proposal but with the optional
> symbol on the inside, a mandatory whitespace
> > after the symbol, and no whitespace after the : right?
> > {:lid|x␣string x|}
> >
> > no whitespace, we need the *precise location*, whitespace will introduce
> trouble here
> > The optional *character set is limited to [/+-] (serveral more)*, only
> those optional characters will be recgonized.
> > so you can still write {:json|{a;b}|}
> > but {:json|/{a;b|}}/|} also works
>
> Without a whitespace how do you know if the '/' is your optional character
> or part of the quoted syntax?
> (unless you restrict the quoted syntax's first character to be something
> else than the optional characters)
>
> exactly( optional chars is a limited set, but is enough in
practice,(stolen from perl)
> What do you think of this syntax:
> {:lid|...|lid:}
>
> no, we introduce Language namespace, sometimes you can write unamed
quotations XD
> Its still quite easy to find where quotation's bounds are, it is
> symmetric, and the end marker should be long enough
> to not cause false matches inside the quotation.
>
> Best regards,
> --Edwin
>
--
-- Regards, Hongbo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/wg-camlp4/attachments/20130131/022f8d19/attachment.html>
More information about the wg-camlp4
mailing list