problems with mixins and non-ascii characters

2014-01-22 Thread Uplink_Coder

Hi,
When I try to define an Enum with an umlaut like ä

enum test2 {
l,
ä
}
I get  Error: basic type expected, not \u00e4
and Error: type only allowed if anonymous enum and no enum 
type


is there any workaround for this ?


Re: problems with mixins and non-ascii characters

2014-01-22 Thread Benjamin Thaut

Am 22.01.2014 11:46, schrieb bearophile:

Uplink_Coder:


is there any workaround for this ?


For me this is a feature, not a bug.

Bye,
bearophile


Why that? D is supposed to support unicode identifiers, and in this case 
it cleary does not?


Re: problems with mixins and non-ascii characters

2014-01-22 Thread bearophile

Uplink_Coder:


is there any workaround for this ?


For me this is a feature, not a bug.

Bye,
bearophile


Re: problems with mixins and non-ascii characters

2014-01-22 Thread Uplink_Coder

On Wednesday, 22 January 2014 at 10:46:30 UTC, bearophile wrote:

Uplink_Coder:


is there any workaround for this ?


For me this is a feature, not a bug.

Bye,
bearophile


I never said bug :D
just I thoght UniCode should make this a non-issue ...



Re: problems with mixins and non-ascii characters

2014-01-22 Thread monarch_dodra

On Wednesday, 22 January 2014 at 10:51:54 UTC, Uplink_Coder wrote:

On Wednesday, 22 January 2014 at 10:46:30 UTC, bearophile wrote:

Uplink_Coder:


is there any workaround for this ?


For me this is a feature, not a bug.

Bye,
bearophile


I never said bug :D
just I thoght UniCode should make this a non-issue ...


It's a bug. ä is a valid identifier.


Re: problems with mixins and non-ascii characters

2014-01-22 Thread Uplink_Coder
 Strange this bug seems to manifest itself only in some 
situations

enum ä {ä = ä}
does not work in dpaste but suddenly it works on my local 
enviorment (Windows-Mono-d,dmd 2.064.2)


it seems to have something todo with the abscence of a BOM header 
...