178200 - need new C++ portability doc

Status: RESOLVED FIXED

(Developer Documentation Graveyard :: Mozilla Platform, defect, P5)

Description

[Scott Collins]

Our old doc is woefully out of date.  We can't write this doc alone.  We need to
build tests, list the compilers, etc.  I'd like to do this `autoconf style'.  If
that makes any sense.  Anyway, I needed a bug to remind me to get on this.

Comment 1

[Nicos Gollan]

There are a few extremely ridiculous parts in the guidelines. My favorites are:

 * Don't use C++ standard library features, including iostream
That's probably the single most retarded thing I've read in a long time. It's called "C++ Standard Library" for a reason. If you don't use it, don't pretend to write C++.

 * Don't use namespace facility
"Relatively new"? No. If you say that, you might as well forbid the use of other "relatively new" features, such as the bool type, or classes.

In my opinion, those guidelines are giving way too much leeway to old and exceedingly broken compilers, and needlessly endanger the userbase. This is especially true of ignoring the C++SL, since that requires reinvention of quite a few wheels instead of relying on proven implementations.

Comment 2

[David Boswell]

These docs are now on MDC at

http://developer.mozilla.org/En/C___Portability_Guide

Moving bug to Mozilla Developer Center product for discussion.

Comment 3

[John Karahalis [:openjck]]

Automatically closing all bugs that have not been updated in a while. Please reopen if this is still important to you and has not yet been corrected.

Comment 4

[John Karahalis [:openjck]]

Reopening for review by Sheppy.

Comment 5

[Eric Shepherd [:sheppy]]

This article seems to have disappeared; can someone on the MDN dev team help get it back

Comment 6

[John Karahalis [:openjck]]

Sheppy: See bug 780363.

Comment 8

[Eric Shepherd [:sheppy]]

Oops, misread. Not a dupe after all.