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,
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
> 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
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."
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
Thanks Jim. I recorded this policy in JEP 12, under "Relationship to
Java SE APIs":
"The API developer must also add an @since tag that indicates the
release when @preview was first added. (If the essential API element is
eventually made final and permanent in Java SE $Z, then the @since tag
FTR: A question was raised about which Java version should be used with the
@since tag of method associated with a preview feature. The evident answer is
that while previewing, that the value should be the version of Java where the
preview feature was introduced. When the feature becomes
>> #1. Accessibility of various record members.
Let’s write down the various (competing) considerations here:
- Consistency with precedent of default constructors. When the compiler fills
in a default no-arg constructor in a class that has no constructors, the
default constructor gets the
- Mail original -
> De: "Gavin Bierman"
> À: "amber-spec-experts"
> Envoyé: Lundi 6 Avril 2020 12:10:55
> Objet: Final issues regarding records
> Dear Experts:
>
> I’d like to circle back on a couple of issues regarding records. I am
> finalizing
> the draft language spec - would
Dear Experts:
I’d like to circle back on a couple of issues regarding records. I am finalizing
the draft language spec - would really like to complete this very soon - so it
would be great to get some EG feedback so we cancomplete the spec (and tweak
the implementation as necessary). I'm
10 matches
Mail list logo
