Re: [Corelinux-develop] Fwd: Comments and question on the corelinux++ coding standards

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> ----------  Forwarded Message  ----------
> Subject: Comments and question on the corelinux++ coding standards
> Date: Tue, 5 Sep 2000 14:52:48 +0100 (GMT+01:00)
> From: Robert Marshall <ra...@fs...>
> To: pru...@us...
> 
> I've used this document as a basis for designing our own standards (thanks
>  very much). I hope you don't mind if I ask some questions and make a few
>  comments on that document.
> 
> - standard 1 referes to the Venice coding standards. Is this a publically
>  available document? I couldn't find any references to it on the internet. -

Man, this is what happens when I take the dust off of things that were
new back then :). I will have to find something more timeless.

>  Guideline 16 is really a rationale for the previous standard (33) rather
>  than a guideline in itself.

Guideline 16 is a typo, should be Rationale

> 
> - the formatting of the html makes the examples in standards 34-36
>  meaningless. 

Agree

> - Standard 60 and guideline 40 seem to be in conflict

These are some of the compromises made from other feedback. Basically it
is saying "avoid it as people may turn of RTTI", but at the same time if
working around it means crap code, then use it.

> - standard 67, I'd add the words `and unimplemented' to the second sentence
>  for clarity. 

Umm, we still would "implement" them even if they are private. We do not
want the compiler defaults to take over.

> - the reference to sourceware.cygnus.com is dated with the
>  takeover by redhat. Again couldn't find the template standards being
>  referred to here, if you could point me in the right direction I'd be very
>  grateful! 

Agreed. will have to track it down.

> - Have grave doubts about standard 114 with the current state of
>  exception specification support. 

But getting better all the time! This is also a compiler vendor issue,
as we are mapping to the standard.

>  I'm curious that namespace and template
>  mention is very scant but there's this reference. - The bibliography appears
>  to reference itself (I suppose though it tells you where to get the
>  original) - I'm looking at developing standards for the use of the STL do
>  you know of any existing guidelines for this. - the comments to webmaster at
>  the foot of the page refers to sourcefforge. (apologies if this was a
>  deliberate spam beater) - miscellaneous typographical errors.

Typo, as _at_ foils the agents.

> 
> Thanks for reading this far!
> 
> Robert
> 
> _______________________________________________________________________
> FSmail - Get your free web-based email from Freeserve: www.fsmail.net
> 
> -------------------------------------------------------
> 
> --
>   Christophe Prud'homme                  |
>   MIT, 77, Mass Ave, Rm 3-243            |   If it doesn't work, force it.
>   Cambridge MA 02139                     |   If it breaks, it needed
>   Tel (Office) : (00 1) (617) 253 0229   |   replacing anyway.
>   Fax (Office) : (00 1) (617) 258 8559   |
>   http://augustine.mit.edu/~prudhomm     |
>                           Following the hacker spirit
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package