On May 8, 2020, at 12:59 PM, fo...@univ-mlv.fr wrote:
>
>
> I'm not against replacing "type" as a generic term for all the construct.
> You're using "type-declaring construct", and i think it's a better term that
> "class and/or interface" because it convey the fact that this is an union of
>
On 5/8/20 12:02 PM, Dan Smith wrote:
On May 8, 2020, at 11:26 AM, Jonathan Gibbons
wrote:
On 5/7/20 11:48 AM, Dan Smith wrote:
This isn't a one-time change. I'm sure there's more work to do in JLS and JVMS,
as the need arises, and various other parts of the ecosystem (reflection APIs,
> De: "John Rose"
> À: "Remi Forax"
> Cc: "daniel smith" , "amber-spec-experts"
>
> Envoyé: Vendredi 8 Mai 2020 02:15:44
> Objet: Re: Class & interface terminology
> On May 7, 2020, at 3:07 PM, [ mailto:fo...@univ-mlv.fr
> On May 8, 2020, at 11:26 AM, Jonathan Gibbons
> wrote:
>
> On 5/7/20 11:48 AM, Dan Smith wrote:
>> This isn't a one-time change. I'm sure there's more work to do in JLS and
>> JVMS, as the need arises, and various other parts of the ecosystem
>> (reflection APIs, javac error messages,
> On May 7, 2020, at 6:57 PM, fo...@univ-mlv.fr wrote:
>
> Yes, the JLS explicily says that an annotation type is an interface so it's a
> reified type, you can create array of them and declare member types in it
> (even i never seen a code like that),
> all other things are different,
So it
On 5/7/20 11:48 AM, Dan Smith wrote:
This isn't a one-time change. I'm sure there's more work to do in JLS and JVMS,
as the need arises, and various other parts of the ecosystem (reflection APIs,
javac error messages, javadoc output, JDK code internals, third-party tools,
etc.) may want to
On 5/7/2020 4:19 PM, Alex Buckley wrote:
We ought to be able to represent the taxonomy in a table, where any
combination of row title and column title gives something meaningful:
| Declaration | Type
-
Class C
- Mail original -
> De: "daniel smith"
> À: "Remi Forax"
> Cc: "amber-spec-experts"
> Envoyé: Vendredi 8 Mai 2020 01:11:48
> Objet: Re: Class & interface terminology
>> On May 7, 2020, at 4:07 PM, fo...@univ-mlv.fr wrote:
>>
On May 7, 2020, at 3:07 PM, fo...@univ-mlv.fr wrote:
>
> No, i disagree about to things
> - trying to tilt each features to be either an interface or an class is not
> appropriate
I buy Dan’s argument that since the JLS uses this bifurcation,
it is legitimate to extract more benefit from it in
On May 7, 2020, at 4:11 PM, Dan Smith wrote:
>
> I feel strongly that "class or interface" is better than "type", and that we
> need to stop using "type" in this context. I'm agnostic about what we say
> instead. But "class or interface" has the benefit that it's already used
> pretty
On 5/7/2020 3:24 PM, Dan Smith wrote:
Are you comfortable with the tension between "annotation interface
declaration" and "enum declaration", or do we need to keep pulling on
the string to get "enum class declaration"?
As weird as "annotation interface declaration" is, there has to be some
> On May 7, 2020, at 4:07 PM, fo...@univ-mlv.fr wrote:
>
> - Mail original -
>> De: "daniel smith"
>> À: "Remi Forax"
>> Cc: "amber-spec-experts"
>> Envoyé: Jeudi 7 Mai 2020 23:06:44
>> Objet: Re: Class & i
> On May 7, 2020, at 4:08 PM, Alex Buckley wrote:
>
> On 5/7/2020 2:29 PM, Dan Smith wrote:
>> Is there a particular part of JLS that you think should be rephrased to
>> reflect these assertions?
>
> No, I just wanted to get the assertions on the record in email, so they
> could be added to
On 5/7/2020 2:29 PM, Dan Smith wrote:
Is there a particular part of JLS that you think should be rephrased
to reflect these assertions?
No, I just wanted to get the assertions on the record in email, so they
could be added to the discussion at the start of the Consistent
Terminology spec. 10
- Mail original -
> De: "daniel smith"
> À: "Remi Forax"
> Cc: "amber-spec-experts"
> Envoyé: Jeudi 7 Mai 2020 23:06:44
> Objet: Re: Class & interface terminology
>> On May 7, 2020, at 1:47 PM, Remi Forax wrote:
>>
> On May 7, 2020, at 3:02 PM, Alex Buckley wrote:
>
> Speaking of "generic", I would be grateful if you can clarify (maybe here, in
> the first instance, then later in the draft) :
>
> - A generic class or interface declaration begets a generic class or
> interface. (1.1 "Class and interface
> On May 7, 2020, at 1:47 PM, Remi Forax wrote:
>
> There is a good reason why it is done that way, i.e. enum is called enum and
> not enum class or annotation type is not called annotation interface.
> It's to avoid the confusion between the feature of the language and its
> translation
On 5/7/2020 11:48 AM, Dan Smith wrote:
I'll add that it's useful to think in terms of three different entities:
1) Class and interface declarations. These are syntax. Example: "interface List
..."
2) Classes and interfaces. These are "symbols". Example: the interface List
3) Class and
- Mail original -
> De: "daniel smith"
> À: "amber-spec-experts"
> Envoyé: Jeudi 7 Mai 2020 20:48:41
> Objet: Class & interface terminology
> We've made some efforts recently to make more precise usage of the terms
> "class", &
19 matches
Mail list logo
