True enough on the C++, however, this is actually viewed as a design flaw by many, as it creates ambiguity in the language and other problems.

A lot of people never really think about this, as it's easy enough to pick implementations that makes sense... but have you ever seen code that one minute tries to use cout, or cerr, and the next min fprintfs to stout n stderr? That's solvable enough, but what about creating an object from a c header with a function that exit(1)'s, which is obviously inappropriate, and now should be handled differently... or when people mix using C code and methodology with C++. Everbody's been stuck debugging code at some point in their life that somehow has a linked list of objects in it (the linked list being started with *my_list, the objects being improperly instantiated somewhere, and you with a debugger and a big pot of coffee.

This of course is not to detract from the merits of C++

Just Another Perl Backpacker

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.