[Some sample LE3 code]

Since try/catch can't be done in all languages, there should be an advanced version of the LE2 engine logfile. One that writes all information instantly to the logfile, no matter what errors occurs.

(Is not the case in LE2)

 

And what about an error callback. You could predefine a bunch of errorcodes and the user gets an callback method called, when an error occurs. The method gets the errorcode as a parameter and we could react to a "MeshNotFound" error for example. Would only work if those errors don't kill the engine, though. But it could work in all languages i think.

 

Like most people here i have no problem with -> at all.

[Kabul Street]

Why are you posting photos michael?!? I thought the gallery was for screenshots...^^

[Pump up the volumes]

Sounds Great! (and expensive )

[Building a setup with InnoSetup]

Thanks for your time!

This looks really easy to do

[Picking up speed]

Well doesn't it mean there is some progress?

[Improvements for 2.32]

Now i'm stuck, waiting for this awesome update...

[Pure3D launches realtime division]

Looks like i need to buy this

[To program or not to programm]

When you want to save yourself some headaches, you should start learning the language that will be taught at that academy. I'm sure it will be one of the following: C/C++, Ada or Java

In case you are serious about game programming, there is no way around C/C++. At least that is

what my professor said

My advice is:

Start with C and a classical little black DOS window. That way you can learn procedural programming

at the lowest possible level. After that you start using C++ and learn OOP. It's not that hard, but you'll need patience (and a profound understanding of procedural programming )

[Double-buffered shadow maps]

Sounds very promising

[The Day After]

Lua is very nice to get a different properties editor for every entity.

For the rest i will still take C++ and retrieve the keys from the .sbx.