BO> -void _seg * KernelAllocPara(size_t nPara, UBYTE type, CStr name, int mode) BO> +void _seg * KernelAllocPara(size_t nPara, UBYTE type, const char *name, int BO> mode)
This is example, how my shortcuts allows to shorter and, thus, more redable lines.
No, Bart is perfectly right. If you use CStr, I first have to lookup what CStr means. It is no "obvious" name for const char *! This actually INCREASES the problems with reading code, unless you first learn all defines by heart. UBYTE on the other hand, for example, is a very obvious name for something which is not signed and 8 bits big.
Yes, I also agree here. I have used things like that in tha past and in some cases I even replaces them back to "normal". The problem is that this is grat when you are writing and actively debugging the program this is grat, but 1) after a few years and 2) by someone else, it tends to get harder and harder to understand.
One Alternative is to use SetEdit and use itá auto-completion/expand feature to save some typing :)
Alain
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
