All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shriramana Sharma <jamadagni@gmail.com>
To: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: C or C++
Date: Wed, 02 May 2007 19:50:55 +0530	[thread overview]
Message-ID: <46389E47.5040601@gmail.com> (raw)

Hello.

I am writing a library and wondering whether to write it in C or C++. 
Previously I knew only C but now I got introduced to the many 
conveniences of C++ I am loth to give them up. I also feel C++ is a 
cleaner language than C (for whatever reason).

OTOH I am thinking maybe if I write in C many more programmers will be 
able to use it - C programmers as well as C++ programmers, whereas if I 
write in C++ only C++ programmers can use it (i.e. if the API contains 
any C++-specific items [or even if otherwise?]).

I would like the list's opinion on whether it is worth sacrificing the 
advantages of C++ to capture more "clients".

A voice inside tells me -- Qt and KDE are pure C++, yet they are among 
the hugest-used (if there is such a word) libraries... But another voice 
tells me -- there is GTK, GNOME and so many other libraries which I do 
not know which may be having many users precisely because they are in 
pure C...

So I don't want to be like the frog in the well (who did not know there 
was such a thing as an ocean) and so I am asking you.

Namaste.

Shriramana Sharma.


             reply	other threads:[~2007-05-02 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 14:20 Shriramana Sharma [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-04 11:00 C or C++ Shriramana Sharma
2007-05-04 11:17 ` leslie.polzer
2007-05-04 13:46 ` Glynn Clements
2007-05-16 13:44   ` Shriramana Sharma
2007-05-22 18:10     ` Glynn Clements

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=46389E47.5040601@gmail.com \
    --to=jamadagni@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.