Re: allMembers broke for __

2018-06-26 Thread dayllenger via Digitalmars-d
On Tuesday, 19 June 2018 at 12:59:00 UTC, Steven Schveighoffer wrote: I'd recommend putting in an enhancement request in bugzilla. Done: https://issues.dlang.org/show_bug.cgi?id=19028 Really, this behaviour at least should be reflected in `allMembers` and `derivedMembers` documentation.

Re: allMembers broke for __

2018-06-19 Thread Steven Schveighoffer via Digitalmars-d
On 6/19/18 2:23 AM, DigitalDesigns wrote: On Monday, 18 June 2018 at 21:47:01 UTC, Steven Schveighoffer wrote: On 6/18/18 5:27 PM, Walter Bright wrote: On 6/18/2018 3:54 AM, Timon Gehr wrote: The code you linked to does it. :) I know. But it shouldn't. Do as I say, not as I do :-) I don't

Re: allMembers broke for __

2018-06-19 Thread Walter Bright via Digitalmars-d
On 6/18/2018 11:42 PM, aliak wrote: Is the extern(C++) on semanticTraits remnants from converting dmd to d? No, it's to be callable from the 3 non-D back ends.

Re: allMembers broke for __

2018-06-19 Thread aliak via Digitalmars-d
On Sunday, 17 June 2018 at 22:55:57 UTC, Walter Bright wrote: On 6/15/2018 11:08 PM, DigitalDesigns wrote: When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is not aware of the bug. It's not a

Re: allMembers broke for __

2018-06-19 Thread DigitalDesigns via Digitalmars-d
On Monday, 18 June 2018 at 21:47:01 UTC, Steven Schveighoffer wrote: On 6/18/18 5:27 PM, Walter Bright wrote: On 6/18/2018 3:54 AM, Timon Gehr wrote: The code you linked to does it. :) I know. But it shouldn't. Do as I say, not as I do :-) I don't see how you misuse the symbols. I think

Re: allMembers broke for __

2018-06-18 Thread Steven Schveighoffer via Digitalmars-d
On 6/18/18 5:27 PM, Walter Bright wrote: On 6/18/2018 3:54 AM, Timon Gehr wrote: The code you linked to does it. :) I know. But it shouldn't. Do as I say, not as I do :-) I don't see how you misuse the symbols. I think it's more that you shouldn't *define* these symbols, not that you

Re: allMembers broke for __

2018-06-18 Thread Walter Bright via Digitalmars-d
On 6/18/2018 3:54 AM, Timon Gehr wrote: The code you linked to does it. :) I know. But it shouldn't. Do as I say, not as I do :-)

Re: allMembers broke for __

2018-06-18 Thread Steven Schveighoffer via Digitalmars-d
On 6/18/18 12:57 PM, bauss wrote: On Monday, 18 June 2018 at 08:25:46 UTC, Russel Winder wrote: On Sun, 2018-06-17 at 15:55 -0700, Walter Bright via Digitalmars-d wrote: […] Identifiers starting with __ are reserved for the implementation:    https://dlang.org/spec/lex.html#identifiers

Re: allMembers broke for __

2018-06-18 Thread bauss via Digitalmars-d
On Monday, 18 June 2018 at 08:25:46 UTC, Russel Winder wrote: On Sun, 2018-06-17 at 15:55 -0700, Walter Bright via Digitalmars-d wrote: […] Identifiers starting with __ are reserved for the implementation: https://dlang.org/spec/lex.html#identifiers They have implementation-defined

Re: allMembers broke for __

2018-06-18 Thread Timon Gehr via Digitalmars-d
On 18.06.2018 00:55, Walter Bright wrote: On 6/15/2018 11:08 PM, DigitalDesigns wrote: When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is not aware of the bug. It's not a bug, it's quite

Re: allMembers broke for __

2018-06-18 Thread Russel Winder via Digitalmars-d
On Sun, 2018-06-17 at 15:55 -0700, Walter Bright via Digitalmars-d wrote: > […] > Identifiers starting with __ are reserved for the implementation: > >https://dlang.org/spec/lex.html#identifiers > > They have implementation-defined behavior. Do not use them in user code. In delegates I

Re: allMembers broke for __

2018-06-17 Thread DigitalDesigns via Digitalmars-d
On Sunday, 17 June 2018 at 22:55:57 UTC, Walter Bright wrote: On 6/15/2018 11:08 PM, DigitalDesigns wrote: When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is not aware of the bug. It's not a

Re: allMembers broke for __

2018-06-17 Thread Walter Bright via Digitalmars-d
On 6/15/2018 11:08 PM, DigitalDesigns wrote: When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is not aware of the bug. It's not a bug, it's quite deliberate:

Re: allMembers broke for __

2018-06-17 Thread angel via Digitalmars-d
On Sunday, 17 June 2018 at 02:25:59 UTC, Adam D. Ruppe wrote: On Sunday, 17 June 2018 at 01:02:17 UTC, DigitalDesigns wrote: If this was a sane language constraint then any identifiers starting with __ that were not reserved would at least give a warning but particularly give an error! Not

Re: allMembers broke for __

2018-06-16 Thread Jonathan M Davis via Digitalmars-d
On Sunday, June 17, 2018 01:02:17 DigitalDesigns via Digitalmars-d wrote: > On Saturday, 16 June 2018 at 23:33:13 UTC, Jonathan M Davis wrote: > > On Saturday, June 16, 2018 22:59:24 DigitalDesigns via > > > > Digitalmars-d wrote: > >> On Saturday, 16 June 2018 at 06:47:59 UTC, Jonathan M Davis >

Re: allMembers broke for __

2018-06-16 Thread Adam D. Ruppe via Digitalmars-d
On Sunday, 17 June 2018 at 01:02:17 UTC, DigitalDesigns wrote: If this was a sane language constraint then any identifiers starting with __ that were not reserved would at least give a warning but particularly give an error! Not fail silently and break code in ways that cannot be determined

Re: allMembers broke for __

2018-06-16 Thread DigitalDesigns via Digitalmars-d
On Saturday, 16 June 2018 at 23:33:13 UTC, Jonathan M Davis wrote: On Saturday, June 16, 2018 22:59:24 DigitalDesigns via Digitalmars-d wrote: On Saturday, 16 June 2018 at 06:47:59 UTC, Jonathan M Davis wrote: > On Saturday, June 16, 2018 06:08:17 DigitalDesigns via > > Digitalmars-d wrote: >>

Re: allMembers broke for __

2018-06-16 Thread Jonathan M Davis via Digitalmars-d
On Saturday, June 16, 2018 22:59:24 DigitalDesigns via Digitalmars-d wrote: > On Saturday, 16 June 2018 at 06:47:59 UTC, Jonathan M Davis wrote: > > On Saturday, June 16, 2018 06:08:17 DigitalDesigns via > > > > Digitalmars-d wrote: > >> When an identifier starts with __, allMembers does not

Re: allMembers broke for __

2018-06-16 Thread DigitalDesigns via Digitalmars-d
On Saturday, 16 June 2018 at 06:47:59 UTC, Jonathan M Davis wrote: On Saturday, June 16, 2018 06:08:17 DigitalDesigns via Digitalmars-d wrote: When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is

Re: allMembers broke for __

2018-06-16 Thread rikki cattermole via Digitalmars-d
On 16/06/2018 6:47 PM, Jonathan M Davis wrote: On Saturday, June 16, 2018 06:08:17 DigitalDesigns via Digitalmars-d wrote: When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is not aware of the bug.

Re: allMembers broke for __

2018-06-16 Thread Jonathan M Davis via Digitalmars-d
On Saturday, June 16, 2018 06:08:17 DigitalDesigns via Digitalmars-d wrote: > When an identifier starts with __, allMembers does not return it. > This is very bad behavior! It can silently create huge problems > if the programmer is not aware of the bug. > > Instead, if you want to keep the

allMembers broke for __

2018-06-16 Thread DigitalDesigns via Digitalmars-d
When an identifier starts with __, allMembers does not return it. This is very bad behavior! It can silently create huge problems if the programmer is not aware of the bug. Instead, if you want to keep the current behavior at least create an error or warning rather than silently create a bug