Draft language spec for JEP 355: Text Blocks

[Jim Laskey]

Thank you.

> On May 21, 2019, at 4:41 PM, Alex Buckley <Alex.Buckley at oracle.com> wrote:
> 
> On 5/21/2019 5:30 AM, Jim Laskey wrote:
>> TextBlock:
>> 
>> " " " { the ASCII SP character } LineTerminator { TextBlockCharacter } " " "
>> 
>>  "the ASCII SP character" in the open delimiter is currently
>> implemented as any "white space" but not a line terminator. Later on you
>> state "zero or more white spaces".
> 
> Thank you for this clarification. I agree that a text-block-only form of "white space" -- spaces, tabs, form feeds -- can legitimately appear after the """. I have added a production and narrative to capture this.
> 
>> The string represented by a text block is /not/ the literal sequence of
>> characters in the content. Instead, the string represented by a text
>> block is the result of processing the content, as follows:
>> 
>> I think this could be reworded so that the importance of order is made
>> clear. Later on you state "Interpreting escape sequences last allows",
>> but it's still not clear the order of 1 & 2 is important. In the JEP we
>> described them as "steps". Stages might work as well.
> 
> A numbered list in the JLS traditionally means in-order processing, but for the avoidance of doubt I have said "... the result of applying the following transformations to the content, in order:"
> 
> Alex