[Issue 8530] New: Float types default initializers doesn't work in class

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8530

   Summary: Float types default initializers doesn't work in class
   Product: D
   Version: D2
  Platform: x86_64
OS/Version: Linux
Status: NEW
  Severity: major
  Priority: P2
 Component: DMD
AssignedTo: nob...@puremagic.com
ReportedBy: kozz...@gmail.com


--- Comment #0 from Daniel Kozak kozz...@gmail.com 2012-08-10 02:27:21 PDT ---
Created an attachment (id=1136)
problematic code

When I create class with some float variable without value, then call some
method on this class and test float variable for default value, it doesnt work.

My code is in in attachment

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8530] Float types default initializers doesn't work in class

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8530


Jonathan M Davis jmdavisp...@gmx.com changed:

   What|Removed |Added

 CC||jmdavisp...@gmx.com


--- Comment #1 from Jonathan M Davis jmdavisp...@gmx.com 2012-08-10 03:00:35 
PDT ---
If you want to check for NaN, then use std.math.isNaN. As I understand it,
there is no guarantee that two NaN values have the same bit pattern (at
minimum, you have signed and unsigned NaN, and there may be more variations - I
don't remember). isNaN returns true in both cases. So, I don't believe that
this is a bug.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8531] New: formatting string documentation

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8531

   Summary: formatting string documentation
   Product: D
   Version: D2
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Phobos
AssignedTo: nob...@puremagic.com
ReportedBy: bioinfornat...@gmail.com


--- Comment #0 from bioinfornatics bioinfornat...@gmail.com 2012-08-10 
03:39:04 PDT ---
Dear,

In this documentation http://dlang.org/phobos/std_format.html#format-string
They do not talk about %u for unsigned number. %u works well with both readf
and writef

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8532] New: Pure Segfault

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8532

   Summary: Pure Segfault
   Product: D
   Version: D2
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: DMD
AssignedTo: nob...@puremagic.com
ReportedBy: daniel...@bigpond.com


--- Comment #0 from Daniel daniel...@bigpond.com 2012-08-10 03:44:26 PDT ---
auto sum(Y, R ...)(R r, Y val) pure { return sum(r, val); } // segfault
//auto sum(Y, R ...)(R r, Y val) { return sum(r, val); } // no segfault, just
an error, as it should
void main() { sum(1, 2, 3); }

I first noticed this in 2.059, it remained to 2.060.
http://dpaste.dzfl.pl/74702d88

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8533] Postfix and prefix declarations of static multidimensional arrays aren't equivalent

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8533


timon.g...@gmx.ch changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||timon.g...@gmx.ch
 Resolution||INVALID


--- Comment #1 from timon.g...@gmx.ch 2012-08-10 10:33:29 PDT ---
The documentation doesn't seem to state the equivalence of
int[3][2] m;
int m[3][2];

and indeed the declarations are not equivalent.

int[3][2] m;
int m[2][3];

would be equivalent.

If there is a place in the documentation that does state the first
equivalence, please file a bug against the documentation.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8533] Postfix and prefix declarations of static multidimensional arrays aren't equivalent

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8533



--- Comment #2 from fataler...@trash-mail.com 2012-08-10 11:30:16 PDT ---
Oh, yes it was an oversight on my side, sorry.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


Re: [Issue 8530] New: Float types default initializers doesn't work in class

2012-08-10 Thread Walter Bright

On 8/10/2012 2:30 AM, Daniel Kozak wrote:

Problematic code:


Replying to bug reports in the newsgroup generally means your reply will be 
overlooked. Please reply on bugzilla.


[Issue 8534] New: mixed-in struct definition not forward referenceable

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8534

   Summary: mixed-in struct definition not forward referenceable
   Product: D
   Version: D2
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: DMD
AssignedTo: nob...@puremagic.com
ReportedBy: dmitry.o...@gmail.com


--- Comment #0 from Dmitry Olshansky dmitry.o...@gmail.com 2012-08-10 
13:25:59 PDT ---
Test case:

SimpleCaseEntry[] simpleTable;

mixin(mixedCCEntry);

enum mixedCCEntry = q{
struct SimpleCaseEntry
{

}
};


dmd 2.060 outputs:
forward.d(2): Error: undefined identifier SimpleCaseEntry

Instead it should just work like this version(this is a workaround):

//case folding mapping
mixin(mixedCCEntry);

SimpleCaseEntry[] simpleTable;

enum mixedCCEntry = q{
struct SimpleCaseEntry
{

}

};

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8535] New: perfectly valid uncidoe chars give: Unsupported char xxx

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8535

   Summary: perfectly valid uncidoe chars give: Unsupported char
xxx
   Product: D
   Version: D2
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: DMD
AssignedTo: nob...@puremagic.com
ReportedBy: dmitry.o...@gmail.com


--- Comment #0 from Dmitry Olshansky dmitry.o...@gmail.com 2012-08-10 
14:19:07 PDT ---
When compiling unicode casefolding table (see attach it's a plain string table)
dmd outputs this:

 Error: unsupported char 0x2d17
 Error: unsupported char 0x2c11
 Error: unsupported char 0x2c41
 Error: unsupported char 0xa726
 Error: unsupported char 0xa727
 Error: unsupported char 0x2d18
 Error: unsupported char 0x2c12
 Error: unsupported char 0x2c42
 Error: unsupported char 0x2d19
 Error: unsupported char 0x2c13
 Error: unsupported char 0x2c43
 Error: unsupported char 0xa728
 Error: unsupported char 0xa729
 Error: unsupported char 0x2d1a
 Error: unsupported char 0x2c14
 Error: unsupported char 0x2c44
 Error: unsupported char 0x2d1b
 Error: unsupported char 0x2c15
 Error: unsupported char 0x2c45
 Error: unsupported char 0xa72a
 Error: unsupported char 0xa72b

All of the above a perfectly valid characters, and in fact have mappings lower
case -- upper case. So either DMD reject chars it doesn't know (wrong way - see
Unicode standard) or has broken validiation.

About characters see here :
http://unicode.org/cldr/utility/list-unicodeset.jsp?a=%5Cu2d17%0D%0A%5Cu2c11%0D%0A%5Cu2c41%0D%0A%5Cua726%0D%0A%5Cua727%0D%0A%5Cu2d18%0D%0A%5Cu2c12%0D%0A%5Cu2c42%0D%0A%5Cu2d19%0D%0A%5Cu2c13%0D%0A%5Cu2c43%0D%0A%5Cua728%0D%0A%5Cua729%0D%0A%5Cu2d1a%0D%0A%5Cu2c14%0D%0A%5Cu2c44%0D%0A%5Cu2d1b%0D%0A%5Cu2c15%0D%0A%5Cu2c45%0D%0A%5Cua72a%0D%0A%5Cua72bg=

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8536] New: OPTLINK crash with large fixed-size array

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8536

   Summary: OPTLINK crash with large fixed-size array
   Product: D
   Version: D2
  Platform: x86
OS/Version: Windows
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: Optlink
AssignedTo: nob...@puremagic.com
ReportedBy: bearophile_h...@eml.cc


--- Comment #0 from bearophile_h...@eml.cc 2012-08-10 15:43:19 PDT ---
This program:

uint[1  24] a;
void main() {}


Gives this error:
test.d(2): Error: index 16777216 overflow for static array



While this program:

struct Foo { uint x; }
Foo[1  24] a;
void main() {}


Causes an OPTLINK crash.


I sometimes translate to D some C programs that for performance reasons use
some large global 2D arrays. In D using a global __gshared dynamic array of
dynamic arrays is an option, but this kills some optimizations the compiler is
able to perform thanks to knowing the 2D matrix sizes at compile-time. In my
opinion asking for 50-100 MB static 2D arrays is not that much for a PC with 2+
GB RAM.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---


[Issue 8536] OPTLINK crash with large fixed-size array

2012-08-10 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=8536



--- Comment #2 from bearophile_h...@eml.cc 2012-08-10 19:43:48 PDT ---
Created an attachment (id=1138)
Three C programs that show one effect of static 2D arrays

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---