Re: [Caml-list] Beta release of ppx_string_interpolate, and help needed with ocamlfind/opam

[Jan Rehders <wurstgebaeck@googlemail.com>]

Alain: yes, for the new string literals this issue does not exist (and
they are already supported). But I'd like to keep support for regular
strings, too. I guess I could also simply expand something like
{istr|...|istr} but I think transforming anything that isn't in "my"
annotations is a bad idea.

Btw: anyone tried to use this with opam? I still couldn't get
ocamlfind to find the package after installation (see first mail).

On Mon, Oct 27, 2014 at 5:01 PM, Alain Frisch <alain@frisch.fr> wrote:
> On 10/26/2014 07:20 PM, Jan Rehders wrote:
>>
>> = Using \ instead of $ =
>> Using Swift style \(foo) instead of $(foo) would be nice but will
>> produce warnings from the lexer which I can't suppress w/o suppressing
>> all warnings about invalid escape sequences. Also this requires doing
>> this from the makefile so every user would have to do it. Is there
>> some API I’ve missed to suppress specific warnings on the code inside
>> [%str ..] from ppx filters?
>
>
> You might want to use the new syntax for string literals:
>
>   {| .... |}
>
> or:
>
>   {id| .... |id}
>
> (for an arbitrary id).  Contrary to regular string literals, OCaml doesn't
> apply any lexing convention to the string contents: what you have in the
> Parsetree is exactly the sequence of bytes from the source file.  This
> allows you to use you own conventions:
>
>    \(foo)
>
> Also, you can map in an exact way between from an index in the string to a
> location in the source code (in a regular string, you cannot distinguish
> \065 from A in the Parsetree, which makes this exact mapping impossible).
>
>
> Combined with an extension node, this would give:
>
>  [%str{| blabla \(x) blabla |}]
>
> -- Alain