Re: [Logic-security-developers] Cleaning Up Code

[Greg T. <gre...@ya...>]

The reason we're getting rid of a single include file
is to clarify dependencies. Sure, you can use
namespace if you want (although I doubt it's
necessary), but it's very important that we separate
functionality sets into distinct include files so that
a module only needs to declare the functionality that
it *needs.*

Separate programs aren't that important right now,
although we could do that some time. Ideally, once our
source code is correctly organized, a transition to
separate programs would be a trivial matter.

- Greg


--- Vageli Mouzakitis <com...@ya...>
wrote:

> The following is a list of objectives that should be
> met if you are "cleaning up the code".
> 
> -removal of plugin system (being taken care of)
> -encapsulation of code into classes
> -encapsulation into seperate programs (I no longer
> htink this is a necessity..comments?)
> -commenting code
> -namespaces?
>  -instead of getting rid of the includes.h file, why
> don't we organize it with namespaces?
> 
> -----fixing code to conform with the rules outlined
> in
> the programming conventions document
> 
> --
> Vageli Mouzakitis

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com