Re: [SharpOS Developers] Coding Conventions

2008-01-17 Thread William Lahti
On Jan 17, 2008 8:00 PM, Bruce Markham <[EMAIL PROTECTED]> wrote: > I'm sorta okay with that. Hopefully we won't need this kinda stuff much > longer though. ;-) Right... we might not be able to get rid of them all though. If we can then awesome. -- fury long name: William Lahti handle :: fury f

Re: [SharpOS Developers] Coding Conventions

2008-01-17 Thread Bruce Markham
I'm sorta okay with that. Hopefully we won't need this kinda stuff much longer though. ;-) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120

Re: [SharpOS Developers] Coding Conventions

2008-01-15 Thread William Lahti
How about we just settle for Allocate()+Init() since this isn't a very controversial matter. Each instantiable kernel type (unmanaged), should provide at least: public static Type *Allocate (); public static void Init (Type *type); where Allocate() both allocates and initializes the data. Natural

Re: [SharpOS Developers] Coding Conventions

2008-01-13 Thread Bruce Markham
I agree with the need for a common convention, but my brain is currently drawing blanks on what I think it should be. More thoughts, from others, are obviously welcome... - Check out the new SourceForge.net Marketplace. It's th

[SharpOS Developers] Coding Conventions

2008-01-12 Thread William Lahti
We have a number of different conventions for Alloc() methods on types, here are some of them: public static Type *Allocate (); public static Type *CREATE (); public static Type *Allocate (Type *inst); The first two will usually allocate and initialize a dynamically-allocated blob, whereas the th