Taras,
On Thu, May 6, 2010 at 5:43 PM, Taras <[email protected]> wrote:
> Hi, all!
>
> I started W3AF Developers Guide [0]. Now it is in 90% copy of
> PEP8 (Style Guide for Python Code).
> Guide always contains Plugins and Packaging W3AF sections.
Thanks for a good start, we needed this. Something I would do is
to split this document in three or more:
- introduction
- plugin architecture
- general code convention (which is the one you wrote)
- plugin development convention
What do you think?
> Let's discuss and approve naming conventions for new code.
>
> I suggest:
> - CamelCase for class names (current state as I see is mixedCase)
> - mixedCase for methods, functions and variables
> - Package and Module Names - save current mixedCase?
>
> What do you think about it?
My opinion is that all new code should be underscore_separated,
and that at some point I'll create a mega_script that will translate
all the code from mixedCase to underscode_separated and we are all
going to be much happier :)
Regards,
> [0] https://sourceforge.net/apps/trac/w3af/wiki/DevelopersGuide
>
> --
> Taras
> http://oxdef.info
> ----
> "Software is like sex: it's better when it's free." - Linus Torvalds
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> W3af-develop mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/w3af-develop
>
--
Andrés Riancho
Founder, Bonsai - Information Security
http://www.bonsai-sec.com/
http://w3af.sf.net/
------------------------------------------------------------------------------
_______________________________________________
W3af-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/w3af-develop
