The Aurora Alpha2 version has been updated. Download from the link provided when purchasing.
Changes:
-----------
- Fixed the pointer deref bug that Parker found...which is the primary reason for the update ;)
- Included the missing dllstartup.o file so you can create DLL's.
- Included the missing resource and assembler dcoumentation.
- Add the advanced listview demo to the example programs.
I guess it never ends ;)
This update gave another bug.
The dictionary class I had complains with a typecast must be specified error on this line:
node->*key = key;
The original said *node.*key = key; since we didn't have -> at that time, the whole source is on these forums.
But other than that, all my other problems are working. Again, it's the (string) must be added problem.
Thanks for the quick update.
Maybe because your using a generic pointer in your node? Written before we had defined pointers maybe?
struct DictNode
{
pointer key;
pointer value;
}
Would probably work if you did this:
struct DictNode
{
string *key;
pointer value;
}
Didn't try it yet.
Yep, it works. I hadn't modified that code for a long time, and I don't know what was making it work before.
Thanks, nevermind that bug then ;)
No problem ;)
And it works more like it should now. POINTER should be treated just like a void * pointer in C. In my other languages we didn't have typed pointers so the compiler would 'guess' the type when the pointer was assigned something. Forcing us to do things like:
pointer p
p = new(char,100)
settype p, STRING
#p = "hello"
Because the pointer would be given the type of 'char'. Typed pointers are more readable and, now that they are working correctly with NEW, more usable.
string *p;
p = new(byte,100);
*p = "hello";
What I should do is remove that automatic type passing during assignment. Forcing typecasting on void pointers. It may eliminate future problems.
QuoteWhat I should do is remove that automatic type passing during assignment. Forcing typecasting on void pointers. It may eliminate future problems.
I'd have to agree there, when the compiler does hidden things like that, it makes it harder to find the bug. Even if it does require more typing.
Paul,
just a quick comment/question here. Would it be possible to update the "About" menu item on the IDE to reflect the release date & time of the alpha? Or would it be possible to label it "Alpha 2.1"? Or is this not the correct SOP for alpha releases. Also is this an Alpha 2 of the compiler or just the IDE?
I'm not trying to make your work any more difficult than it is. Lord knows, I cannot hold a candle up to your programming skill. I'm haven't even attempted a "Hello World" program in Aurora yet. I've blown the dust off of my "Teach yourself C++" book and have wandered around the forum the last couple nights trying to get up enough nerve to try something.
It is alpha 2 of the whole project. An yes I can add more information to the about box, as long as I remember to update it each time ;)
I still have to buy me a C++ book, I only got Kernighan and Ritchie's The C Programming Language, which I think is excellent. Forcing us to use pointers as they should be used is great, thanks Paul!
Speaking of books. I found a website with a ton of e-books for programming, and yes... All free!!! There are a large selection of C, C++ and more.
I will dig out the link as its on my other machine.
Lewis
Somebody'll need to write a book about Aurora one of these days ;)
It would be good if we could write a book for Aurora.
Lewis