So thrdobj.c is more descriptive than for example
ps/thread.c? Hmmm!?
We would still have thread.c.
thrdobj.c would fex. just include code to manage the ObjectManager type
"PsThreadType", for the moment being only PsInitThreadManagment and
PiDeleteThread, but later when/if security functions etc. are added it might
make more sense. It's almost eqvivalent to putting a class and its member
functions into an own file.
Anyways, this is just a suggestion. The reason for this proposal was that i
looked thru the thread/process code, and i see stuff that looks like it
belong into the ctor/dtor of an object. Having own files for types
w/functions might make this more clear.
Nt reorg. update:
-some wants to keep nt functions where they are (currently they are in \nt
and spread around in misc. files)
-some wants to move nt functions into end of files in related subsystems
(nt\ntsem.c -> ke\sem.c etc)
-some wants to move nt functions into related subsystems, but in own files
(nt\ntsem.c -> ke\ntsem.c etc)
Hmmmmm........
Regard
Gunnar
Regards,
Eric
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev