[wg-camlp4] On domain-specific foreign syntaxes

Leo White lpw25 at cam.ac.uk
Fri Feb 1 13:55:12 GMT 2013

>Alternatively, if we choose to make "type extension = longident * 
>expression option" as you suggest, we can also support a different syntax:
>  (# e)  ====>  (* empty identifier in the Parsetree *)
>but this sounds a little bit less natural to me.  I like the 
>minimalistic approach of having "extension = expression" in all 
>syntactic categories (including expression themselves).  But I will 
>certainly not fight the other solution.

If you don't particularly mind, I would prefer this way as I think that it 
will encourage people to name their extensions.

More information about the wg-camlp4 mailing list