> KISS? If it ain't broke? > I am not sure making these routines C++ will be worth it. I don't > see any real improvement at all if using a class instead of the way > it is handled now. I don't mean to tell you not to do this, I just > don't think it will be worth your effort. > > What is your main platform & compiler you use anyway? > > Has any decision been made how the SVN tree is going to be handled? > Are we going to go with all modifications go in as now? Or are we > going to do a testing branch(es?)? IMO everything should go into the trunk and that's how we do it currently. If something needs development over a longer time, for whatever reason, it should go into a branch, so the trunk can still be developed on by others.
I am currently working (actually "was", now I am back to learning for exams) on a replacement for the resourcehandler. I am doing this in a Monotone tree locally, so I am not using a SVN branch either. It is much too early for that. Till nothing more than a raw handler exists, which is still being heavily worked on. No changes to the WZ code has been made, yet. So there are different approaches, but I think "total conversions" (like mine) should be kept out of the trunk till they are so much stabilized that it can be assumed that they will do their job as expected. (That doesn't mean that they are bugfree, though. ;) ) > From back reading logs, this bring up heated discussions about > this, on how some don't want the main branch being messed with, and > others don't care. I think this should be straighten out first > before anymore stuff is changed drastically. Like the memory pool > replacing. We just don't know enough on how all this code works > together. This is ALL Spaghetti code, and we have no way to test > everything before submitting to svn. :(
pgpwVvZ9cWXZL.pgp
Description: PGP signature
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
