Hi,
I will see to the instruction and will take care of completing the task as
early as possible. I have made some changes and have comitted them through
CVS. Please take a look and deliver some feedbacks. Rest after I do some
more work...
Amar
On 9/22/05, log...@li... <
log...@li...> wrote:
>
> Send Logic-security-developers mailing list submissions to
> log...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/logic-security-developers
>
> or, via email, send a message with subject or body 'help' to
> log...@li...
>
> You can reach the person managing the list at
> log...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Logic-security-developers digest..."
>
>
> Today's Topics:
>
> 1. Cleaning Up Code (Vageli Mouzakitis)
> 2. Re: Cleaning Up Code (Greg Toombs)
>
> --__--__--
>
> Message: 1
> Date: Wed, 21 Sep 2005 19:05:37 -0700 (PDT)
> From: Vageli Mouzakitis <com...@ya...>
> To: log...@li...
> Subject: [Logic-security-developers] Cleaning Up Code
>
> 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
>
>
> --__--__--
>
> Message: 2
> Date: Wed, 21 Sep 2005 23:53:44 -0400 (EDT)
> From: Greg Toombs <gre...@ya...>
> Subject: Re: [Logic-security-developers] Cleaning Up Code
> To: Vageli Mouzakitis <com...@ya...>,
> log...@li...
>
> 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
>
>
>
> --__--__--
>
> _______________________________________________
> Logic-security-developers mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/logic-security-developers
>
>
> End of Logic-security-developers Digest
>
--
This mail is from Amar Gautam [CapC]
|
