The thrill is gonne!
No, not the thrill for D, the thrill for the next release of DMD.
We (I) no longer wait for the next release of DMD.
I don't expect amasing new features,
or even the fixes I've been waiting for months
(for which I couldn't produce code examples).
This is to be expected as DMD is reaching 1.0.
Can it be the reason the trafic is slower here?
I bet it is. There is nothing new to see here.
I see this as a good sign. It means DMD is getting there!
Now if I was responsable for D and DMD I would release it without:
(each one insert your own - I'm working on leds)
I'm going to download DMD 0.107 now just to help
finding problems, not because I expect any improvement,
I'm actually afraid things might break...
Thanks for D, Walter.
Ant

Please don't do that yet; I just sent you a problem with dmd-107. It breaks
all the ICU bindings ...
"Walter" <newshound digitalmars.com> wrote in message
news:coh201$2vv3$1 digitaldaemon.com...
|
| "Ant" <duitoolkit yahoo.ca> wrote in message
| news:pan.2004.11.30.04.04.24.396981 yahoo.ca...
| > Now if I was responsable for D and DMD I would release it without:
| > (each one insert your own - I'm working on leds)
|
| Maybe I should just call it 1.0 and ship it!
|
|

Please don't do that yet; I just sent you a problem with dmd-107. It breaks
all the ICU bindings ...

yeah...
but the strategy must be lined up!
Ant

"Walter" <newshound digitalmars.com> wrote in message
news:coh201$2vv3$1 digitaldaemon.com...
|
| "Ant" <duitoolkit yahoo.ca> wrote in message
| news:pan.2004.11.30.04.04.24.396981 yahoo.ca...
| > Now if I was responsable for D and DMD I would release it without:
| > (each one insert your own - I'm working on leds)
|
| Maybe I should just call it 1.0 and ship it!
|
|

Please don't do that yet; I just sent you a problem with dmd-107. It breaks
all the ICU bindings ...

I think Walter was joking. For those who haven't seen it already, we
have a list of reasons we're far from ready for 1.0:
http://www.wikiservice.at/wiki4d/wiki.cgi?PendingPeeves
Stewart.
--
My e-mail is valid but not my primary mailbox. Please keep replies on
the 'group where everyone may benefit.

Can't you do better then that?
The quality of it is very low.
1 - Walter expressly said he didn't want bug lists
2 - points to all sorts of less then relevant discussions

I don't see what you mean. Please be specific.

I think Ant is remembering it wrong.
Walter has said that's he's not going to have an official list of bugs:
"I published a carefully documented bug list once in the past. It was a
disaster." (D/23404)
I don't think he minds it if we keep unofficial bug lists.

I think Ant is remembering it wrong.
Walter has said that's he's not going to have an official list of bugs:
"I published a carefully documented bug list once in the past. It was a
disaster." (D/23404)
I don't think he minds it if we keep unofficial bug lists.

Also, Thomas Kühne is doing an excellent job by keeping an
*automated* bug list in the form of the Dstress test suite:
http://svn.kuehne.cn/dstress/www/dstress.html
That makes it easy to test that old bugs hasn't "resurfaced",
as they have a tendancy to do if not properly pesticided...
--anders

I think Ant is remembering it wrong.
Walter has said that's he's not going to have an official list of bugs:
"I published a carefully documented bug list once in the past. It was a
disaster." (D/23404)
I don't think he minds it if we keep unofficial bug lists.

Also, Thomas Kühne is doing an excellent job by keeping an
*automated* bug list in the form of the Dstress test suite:
http://svn.kuehne.cn/dstress/www/dstress.html
That makes it easy to test that old bugs hasn't "resurfaced",
as they have a tendancy to do if not properly pesticided...

If unittests were applied as advertized, then any error would result
in one ore more unittests written, that would effectively hinder the
errors to return.

That makes it easy to test that old bugs hasn't "resurfaced",
as they have a tendancy to do if not properly pesticided...

If unittests were applied as advertized, then any error would result
in one ore more unittests written, that would effectively hinder the
errors to return.

Dstress is such a unittest, for the compiler itself...
(Thomas has added all kinds of conformance tests,
as well as various bugs reported on the D forums)
All the tests are available at:
http://svn.kuehne.cn/dstress/
The built-in unittest{} is also useful for testing code,
as of DMD 0.108 the following seems to have such tests:

At least, that is what running a quick "grep" told me :-)
I am not sure if either of the testsuites is run before releases,
think that Walter has some kind of internal test program for DMD ?
GDC has a "make unittest", but I've not been able to make that
run, and it doesn't seem to like the GCC "make check-d" either ?
--anders

I got this message from the compiler (which I can ignore obviously)
"Creating default this(){} for class NB"
NB is a nested class.
---------
also found (thanks to 107):
- duplicated char[] switchcase
- passing -1 to uint param
- using inExpression as bit
all my projects seem to run correctly with 107.
(15 min tests...)
for DUI users: all the erros found were in leds,
so no problems with the released DUI and dool.
Ant

For lazy people with Newsreaders:
New/Changed Features
- Improved speed of writef().
- Improved single thread performance of gc allocation per davejf's
suggestions.
- InExpressions now, instead of returning a bit, return a pointer to the
associative array element if the key is present, null if it is not. This
obviates - the need for many double lookups.
- .offset property is now deprecated, use .offsetof instead. This makes
for better compatibility with C and fewer conflicts with offset as a field
name.
- Added .ptr property to arrays, which is handier and more typesafe than
casting an array to a pointer.
- Added Ben Hinkle's changes to std.stream:
adds EndianStream for BOM and endian support.
removes the two public imports std.string and std.file from end of file
adds read/write for ifloat, idouble, cfloat, cdouble and dchar to
interfaces InputStream and OutputStream and add implementations to Stream
and EndianStream
- Added std.c.stddef for definition of C wchar_t.
Bugs Fixed
- Fixed internal error e2ir 814
- Fixed protection of implicit constructor.
- Fixed deprecated attribute overriding static.
- Tightened up detection of constants being implicitly converted to a type
that cannot hold it.
- Now detects duplicate case strings in switch statements.
- Added support for switch(dchar[]) statements.
- Fixed bug reading source files without B.O.M.
- Fixed initialization of anonymous structs in classes.
- Anonymous structs/unions can now only be a member of an aggregate.
- Assert expressions are no longer evaluated for side effects even if
asserts are turned off. It is not legal to depend on the side effect of an
assert.
- Fixed _init vs __init prefix for TypeInfo classes.
- Adjusted arithmetic conversion rules to match C99.
Get it at: ftp://ftp.digitalmars.com/dmd.107.zip
--
"Unhappy Microsoft customers have a funny way of becoming Linux,
Salesforce.com and Oracle customers." - www.microsoft-watch.com:
"The Year in Review: Microsoft Opens Up"

The InExpression yields a boolean result indicating if a key
is in an associative array or not:
if ("hello" in b)
...

The InExpression yields a pointer to the associative array element if
the key is present, or null if the key is not in the associative array.
if (("hello" in b) != null)
...
Assuming you want to pretend that there actually is a boolean type.
Not that D cares about the difference between the two, but anyway.
--anders
PS. Still no way to perform a static init of an associative array ?

I've heard complaints of this before: compilation taking upwards of 2 minutes
under certain circumstances. I just ran into this problem myself with 0.107
under Linux. I have no idea what could be causing this, but I am willing to
share my code if someone wants to check it out. The program is perfect syntax
and semantics, nothing wrong with it; it just won't compile! It worked fine
(read compiled blazingly fast) before I made a few changes and I've been trying
to figure out what those changes were that did it in.
Regards,
James Dunne