groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: println slashy string
Date Wed, 07 Dec 2016 20:55:17 GMT
That is the current expected behaviour. The grammar currently doesn't
support slashy syrings straight after println unless you add the
parentheses. I can't recall the rationale just now. Perhaps it's something
we could look at in the Parrot parser - or an attempt to add it might make
it clear what the rationale is/was.

Cheers, Paul

On 8 Dec 2016 5:53 AM, "Imholz, John J." <imholzj@musc.edu> wrote:

> This message was sent securely by MUSC <http://www.musc.edu/>
>
> This one line script fails for me:
>
> ---BOF---
>
> println /stuff/
>
> ---EOF---
>
>
>
> Causes an error: org.codehaus.groovy.control.
> MultipleCompilationErrorsException: startup failed:
>
> /tmp/println.groovy: 2: unexpected token:  @ line 2, column 1.
>
>
>
> I find using the slashes is helpful when generating some debugging output.
>
>
>
> jji
>
>
>
>
>
>
>
> -------------------------------------------------------------------------
> This message was secured via TLS by *MUSC <http://www.musc.edu>*.

Mime
View raw message