All the code I do is for 1.08, I don't have 1.0 installed a y don't see why I should go out my way to support it so I agree with you decision. All definitions In 1 file sounds good so it's easier to keep open as we just let people know what lines to add.
I also tossed the include guards and just went back to "#pragma once" (original, non-public Yelo code used it). Originally I was trying to keep the code usable under any compiler but just said fuck it, as the game was compiled against the VC++ compiler and they used the Visual Studio IDE. Plus I'm a "Microsoft Specifc" whore %-)
Another benefit with just landing on VC++ as the only supported compiler is the use of a precompiled header. I know most modern compilers support them, but I don't know how others (ie, GCC) require you to set them up and didn't feel like wasting (well, dedicating) time researching if its a standard across all compilers. For other projects I would, but not for this one.
Then of course I'm now making use of the boost preprocessor library. I may find some use of the other sub-libraries in boost before Update 2 is out though. I really just like to keep Yelo's code base really lean as it's interfacing with a black box application so being able to keep any extra code added by the compiler at bay is a must in my eyes. Things like static ctors (which I HATE to begin with) are just a no-no. Object creation\deletion should go in the component initializer and disposer pairs so the system setup and break down are deterministic.
Plus you then just comment a component pair out to quickly find out which system is actually causing a crash at startup and not have to worry about any rogue static initializers defined in a cpp file far, far away, doing some nasty code causing the game to crash. This has saved me time in debugging multiple times. OCD can sometimes be a good thing.
Damn, so much can go on in so little time one is gone. Well It so seems. Kornman00 whether it's me being a pain in everyone's ass or being somewhat of a help. I have been around to see all your achievements, and fails. But you come out on the top, always. I don't know you other than just a forum member, but I want to wish you the best of luck. I want you to step your feet and get into anything you dream. And I believe from what you say it is beginning to happen for you. I'm very glad. And again I wish you best of luck. Hope to see your name somewhere big one day soon man. Though I'm not around in Halo CE anymore. I will miss what you've done and could do for us all. Gonna miss you man!
This isn't the goodbye thread...Originally Posted by Terror(NO)More
Well, technically it is. A little after Update #2 is released, km00 will be parting ways.
Hmm... Hey, km00, you said a week ago you thought you were ready for limited beta, you still thinking about doing that?
What I want to know is if he's still gonna stick around the forums and post from time to time or if he's... REALLY going away forever.
Korny's better than some Halo app imo yeah?
Yeah, I hope he doesn't go away forever :S
While not an officially official good bye thread...yeah. Though I will probably pull a Wolfson every now and then depending on the severity of the need (if I'm still able anyway).
Yeah, I'm getting closer to the date I was hoping to do a limited beta. Never got any mod team PMs though heh.
NOTE: not ignoring other people's posts on purpose...just its not the best time for me to answer things during the work week. I put up with enough shit at work then come home and try to put some work into some things if I can, lurk around and relax.
I'd be happy to test, although you already know my stance on making SPV2 require it.
Another mini-update: I've redesigned the scripting framework internals to now add the custom functions/globals instead of replacing existing "null" ones (functions which didn't do anything per se or globals which didn't reference anything). Just one of the legacy Yelo designs which I wanted to "set right" for the public release. It may have been ok when it was just an internal hack with BB and I, but it wasn't something I would want being the baseline for the public, nor does the old design comply with the compatibility standards I'm setting the OS code to.
The old design was also a reason why a certain scripting extension didn't make it into the initial release...
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Bookmarks