Re: JLS question regarding Text Blocks

2020-04-06 Thread James Laskey
My interpretation was that concludes with a line terminator would make this a non-greedy consumption of white space. But as I said in my response to Dan I didn’t understand white space in spec terms. I had been thinking in terms of the core lib interpretation. Apologies. > On Apr 6, 2020,

Re: JLS question regarding Text Blocks

2020-04-06 Thread Jim Laskey
The spec is correct as-is. I have been made aware that white space in spec terms, as well as the compiler, is only space, tab and form-feed. Other white space (such as non-breaking space, em space, ...) is illegal and produces a javac error. -- Jim > On Apr 6, 2020, at 8:46 PM, Dan Smith

Re: JLS question regarding Text Blocks

2020-04-06 Thread Dan Smith
> On Apr 6, 2020, at 12:43 PM, Jim Laskey wrote: > > In section 3.10.6 Text Blocks of the updated spec; > > "The opening delimiter is a sequence that starts with three double quote > characters ("""), continues with zero or more space, tab, and form feed > characters, and concludes with a

Re: JLS question regarding Text Blocks

2020-04-06 Thread Alex Buckley
On 4/6/2020 11:43 AM, Jim Laskey wrote: In section 3.10.6 Text Blocks of the updated spec; "The opening delimiter is a sequence that starts with three double quote characters ("""), continues with zero or more space, tab, and form feed characters, and concludes with a line terminator."

JLS question regarding Text Blocks

2020-04-06 Thread Jim Laskey
In section 3.10.6 Text Blocks of the updated spec; "The opening delimiter is a sequence that starts with three double quote characters ("""), continues with zero or more space, tab, and form feed characters, and concludes with a line terminator." However, the JEP 378 description reads "The