public inbox for
 help / color / mirror / Atom feed
From: "Saffi Hartal" <>
Subject: Re: biggest deterrant to using C++?
Date: Fri, 14 Aug 1998 10:18:00 -0000	[thread overview]
Message-ID: <003401bdc68a$747568c0$> (raw)

1. C++ is very implicit and therefor dangerous.  Programers must (as always)
know what to do and what to use and more important what not to use
(overloading of casting, calling polymorphic function in constructors,
using bad design with overheads not reasonable ). One should be very

2. The main benefit of C++ is in the application side. C++ have many
benefits that do not come into action if your very near the hardware
(usually) . such benefit is avoiding sending all those parameters by
function because the object know them already, it was constructed or
initialized with the parameters (other way to do that is with annoying
arrays and passing Id's). when you write drivers you usually do it C style
and you prefer that  your colleague would not touch C++ and make annoying

3. In Our Embedded project with vxWorks, I use a bit of C++ when it
convenient, the people around me do not. if there isn't a real benefit it
should not be used. but I do think that using the compiler with strict type
check is good. in future when the need to add polymorphic feature will
arouse we might use much more C++ but very carefully. meanwhile the basic is
C (I do miss the syntax of calling method in Class).

    Don't shoot your leg off by using to much of C++, your fellow men might
not know about the pits of C++ ( i already forgot some of them and believe
me there are many ...).

    maybe with good JITs will do it the Java way.

             reply	other threads:[~1998-08-14 10:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-14 10:18 Saffi Hartal [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-08-26 10:38 Michael Bruck
1998-08-25 18:04 Kenneth Porter
1998-08-25 11:57 Michael Bruck
1998-08-24 18:39 Kenneth Porter
1998-08-23 18:37 Michael Bruck
1998-08-17 16:43 Kenneth Porter
1998-08-14 16:04 Kenneth Porter
1998-08-12 10:44 Brendan Kehoe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003401bdc68a$747568c0$' \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).