www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Re: Walnut, DMD compiler

reply Dan <murpsoft hotmail.com> writes:
jcc7 Wrote:

 == Quote from Dan (murpsoft hotmail.com)'s article
 At the moment, Walnut cannot compile with DMD 1.21 or later because of some bug

 struct Value {
   union {
    struct {}
    int i;
    bool b;
    char[] c;
   bla bla.
 }
 and later doing something with b.  I'd be able to say more, but the error

I worked on reducing the error to a small example, and I filed a related bug: http://d.puremagic.com/issues/show_bug.cgi?id=1738 In the process of reducing the error, I guess I lost some of the context for the error, but I think it seems to be related to the assignment of FALSE in structure.d: # FALSE = { b:false, type:TYPE.BOOLEAN, access:ACCESS.READ },

 Note that I'm not defending that DMD rejects your code. My bug report only
gives
 an example of an error message that should include a line number. I hope this
 helps, but it looks like the compiler is malfunctioning in a couple of ways
when
 it tries to process your code. I only identified one of the malfunctions (lack
of
 a line number).

Ah man. So my program won't work with a modern compiler anymore, and I can't fix my code because I don't know what's wrong with it because DMD doesn't give a useful error message. JCC was good enough to file a bug report for me, but he got no reply for the last two weeks. *sigh* I know it's selfish, but perchance I could beg some help on my project? I can program okay, but I'm not good at all this project management stuff. Sincerely, Dan
Dec 31 2007
parent reply Walter Bright <newshound1 digitalmars.com> writes:
jcc7 Wrote:
 I worked on reducing the error to a small example, and I filed a related bug:
 http://d.puremagic.com/issues/show_bug.cgi?id=1738

This will be fixed on the next update.
Jan 01 2008
parent Dan <murpsoft hotmail.com> writes:
Walter Bright Wrote:

 jcc7 Wrote:
 I worked on reducing the error to a small example, and I filed a related bug:
 http://d.puremagic.com/issues/show_bug.cgi?id=1738

This will be fixed on the next update.

Sweet. Thanks Walter, I appreciate it.
Jan 01 2008