linux-kernel - Re: OT: Open letter to the Linux World

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 04 Sep 2014 10:36:04 -0400
From:	Austin S Hemmelgarn <ahferroin7@...il.com>
To:	Alexander Holler <holler@...oftware.de>,
	Peter Zijlstra <peterz@...radead.org>
CC:	Borislav Petkov <bp@...en8.de>,
	Måns Rullgård <mans@...sr.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Christopher Barry <christopher.r.barry@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: OT: Open letter to the Linux World

On 2014-09-04 06:16, Alexander Holler wrote:
> 
> It's a myth that C++ ends up in bigger code than C. At least in my
> experience. Especially when the latest additions to C++ are in effect
> (like the move-semantics in C++11 I like quiet a lot and which you get
> almost for free (by changing nothing) when you use the STL). Thread
> support is now also standardized (in C++11), quiet nice to use.
Assuming you are writing in a standalone environment (no standard
libraries), then yes, your code will usually be about the same size
(unless you go way overboard with the object-oriented stuff); but the
runtime is larger in almost all non-standalone environments, and there
are some cases that code does end up larger in C++.  A lot of 'Clean C'
(stuff written so that it compiles correctly as C, C++ and Objective C)
that I have seen seems to end up larger (by about 4-6%) when built as
C++ (although it usually does much worse as Objective C).


Download attachment "smime.p7s" of type "application/pkcs7-signature" (2455 bytes)