Hello Arkady, BO>> Or ULONG or u32 or uint32_t or uint_least32_t or simply "unsigned long". BO>> These structures aren't portable anyway. What's in a name?
> Nothing in C/C++ is portable, this is nature of these languages, which > present only machine specific types. But BYTE/WORD/DWORD types are > explicitly developed to ease portability. About uint32_t: good name, but > DWORD (UDWORD) is more traditional. :) the kernel has a 10 year tradition to use ULONG, but you aren't going to play by any rule anyway :(( >>> PS: Do you see the patch from tom, related to unfreed near fnodes at >>> critical handler? BO>> Yes. > And? For me, it looks as "quick and dirty" hack, may be there is better > ways for "garbage collection" over near fnodes? I agree - it's a damned dirty hack. but I haven't found a way so far to do it better - and I *had* to find a solution for this problem. tom ------------------------------------------------------- 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