Re: A C++ Whishlist

From: Johannes Bauer (dfnsonfsduifb_at_gmx.de)
Date: 03/10/04 

Date: Wed, 10 Mar 2004 00:32:16 +0100

Hattuari wrote:

>>These are nothing to do with the language or the standard library. They
>>are to do with your editor or IDE -- moreover they are highly platform
>>specific. This will never happen.
>
>
> Just because it's never been considered or attempted, doesn't mean it can't
> be done. The suggestion comes as a result of a great deal of user-level
> experience with more editors/IDEs than I could possibly name, on several
> different platforms, I should add. I'm not talking about the full
> implementation, I'm talking about the necessary building blocks.

What do you mean? You're proposing changing C++, so why do you add what
  features you'd like to have your IDE in? Do you mean a standard, maybe
appendix, to the C++ standard which declares that keywords like "int",
"float", "double" need to be in green print and "void", "static",
"public" should be blue or mangenta? It's nonsense.

[Snip]

>>The Java String class is useless. Last time I used it (3 years ago) it
>>had an equality operator ('==', although Java doesn't actually support
>>operator overloading) that compared addresses rather than values (in a
>>language that doesn't acknowledge such a thing as an address)!
>>
>>You could do this:
>>
>>String a = "Hello!"
>>String b = "Hello!"
>>
>>The expression "a == b" would return false. No such problems with C++.
>
>
> There is something to be said for RT_M.

Am I missing the point here? I don't know how Java handles a "String",
but if it really compared pointers it would just plain suck. Period. And
Java is annoying enough with its exceptions to the operator overloading
rule (like string concatenation using operator+).

[Snip]

>>What do you mean by automatic synchronization anyway? Sounds like
>>something a tool would do, not the standard library.
>
>
> You say 'the' standard library. But the entire purpose of my post was to
> suggest change.

You haven't answered the question. What do you mean by automatic
synchronizazion? Appearently Pete is not the only one who's confused here...

[Snip]

> What's the point in throwing an exception if
> it isn't handled?

What's the point in "catching" an exception for a statement where you
_know_ no such exception will happen?

One more time answered to some nameless troll. How sad.

Greetings
Johannes 

-- 
"Je ein Stueckchen Kreppsohle an die Fuesse eines Hamsters kleben. Das
Laufrad des Hamsterkaefigs mit Kunststoffteppich auskleiden. Nach 15 bis
20 Minuten Betrieb ist der Elektroschocker geladen und bereit zur
Anwendung."                           Mirko Liss in de.sci.electronics

Relevant Pages

  • Re: UNIX, C, Perl
    ... Nick Keighley wrote: ... snip ... ... how many places can this expression generate an exception? ... especially if operator overloading is present. ...
    (comp.lang.c)
  • Re: A solution for the allocation failures problem
    ... why not just adopt a subset of the C++ exception ... Like throwing specific structs and catch them? ... operator overloading implementation is nothing like C++. ...
    (comp.lang.c)
  • Re: Analyzing this Progression
    ... 7ths of 7th chords resolve downward. ... No, it's not an exception. ... the lower member rises or falls. ...
    (rec.music.theory)
  • Re: When is a function not a function?
    ... a DOM element and Array or a value with falseness. ... assertion that the test betrays poor design. ... assume the worst case (that the exception will be thrown), ...
    (comp.lang.javascript)
  • Re: Jon Skeets thread pooling sample
    ... that decision - I can't think of a good reason why the name of a thread has ... > 4) Add some sort of exception logging for this and the other events. ... It needs to be set before the 1st callback occurs ...
    (microsoft.public.dotnet.general)