So, let's start a discussion about the current nightly build.
I think it will be good for our overview when every question, suggestion and error-report will be posted here in one thread. So after heading forward to a new nightly build this thread can rest in peace.

My first misbehavior report for the nightly build no. 0.5.3.20080704 relates to that fact, that after importing my d-sources to a completely new project all class definitions are marked with the following error-message:

Quote:

"Missing or corrupt object.d"

compilation works fine, it's just the red-dot at the left side of the source plus the red-cross at the package / module in the project-explorer!

EDIT: I've figured out that it must have something to do with the project-building process. Automatic rebuild doesn't work obviously, manual rebuild seams to have not effect, refreshing the project doesn't solve the project. Only after activating "deprecated features" at the project-properties -> D-compiler and the following rebuild the warnings vanished.

Last edited by 3-S-E on Sat Jul 05, 2008 6:48 am; edited 1 time in total

That means Descent can't find "object.d" in your include path, thus nothing will work, because every class extends from Object. I'll make that message be "Missing or corrupt object.d. Make sure you have an "object.d" or "object.di" module in your include path. The easiest way to solve this is to add "Phobos" or "Tango" to the include path."

Okay... maybe you're right and it was just the missing phobos-includepath-entry. But I had the feeling that the rebuild process won't start correctly... But I may be wrong... It's to late now to check if my feeling is right or not!

Because of the formatting-problem: Thanks for solving it!
I am used to to use visibility-attributes because of my computer science study here in Germany. On our university we're programming a lot of C / C++ / Java Stuff with all the design pattern rules... also this attributes.
Now that it's fixed in trunk I have the best feelings for the next nightly build.

But for now I am glad to head off on vacation tomorrow and to turn of my notebook for two weeks!

I know that, but it's a style-question AND I usually have my private (protected) members on top of my class definition, so when I use a "global" attribute-style like "private:" I have to write "public:" below, right!?

Btw: The new nightly build is really fast and a leap forward! Congratulations!

I was going to start implementing new functionalities, but they would be useless if everything was working slowly. So I decided to stop and think about how to make it really fast, then time will come to add features.

As long as the big problem is speed it's ok, because there's always a way to optimize things