If Alex doesnt like it ill revert it in the files that he "own", but this "i own the code" stuff has gone too far.
Any person can see that those macros produce much cleaner code, and without any measureable performance loss. And the stuff with "macros screw my debugging", all list manipulation functions are already macros.
Steven Edwards wrote:
Hi,
--- Alex Ionescu ionucu@videotron.ca wrote:
I don't mind someone using them inside his or her own code. I just mind their usage in ntoskrnl, and even more so when it overwrites the clean, clear code that I've written and am used to debugging.
I think this change should be reverted as well. If Alex is maintaining this code and he does not want to use these macros I don't think we should force them on anyone. While it would be nice to use the Wine list macros in a standard way I just can't agree with it if the people that are hacking on the kernel the most have a problem with it.
Thanks Steven
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev