From: "la deng" <ladeng.mimi@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: c 's OOP in VFS vs c++'s OOP
Date: Fri, 4 May 2007 16:32:27 +0800 [thread overview]
Message-ID: <99e4df080705040132m41116db3y50c73c79528d6206@mail.gmail.com> (raw)
reference to the c++'s father's interview
http://www.artima.com/intv/abstreffi.html
fortran and c++ can achive good performance for they can abstract in
higher level and their compiler can think in higher level to avoid
the cache miss (like in the array vs vector )or to achive the "no
code" Optimization
The vfs using c to OOP but c compiler can't have the high level
Intelligence as the c++ or fortran's compiler to help at the high
level Optimization
one benchmark showed the c insert in the array will slow by speed of 1/17
Then ,what's the power of c OOP vs c++ with the compiler's
Intelligence in OOP?or maybe the c compiler have Outdated?
any input will be appreciated.
next reply other threads:[~2007-05-04 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 8:32 la deng [this message]
[not found] ` <20070504101129.GA5482@localhost.localdomain>
2007-05-04 11:00 ` la deng
2007-05-04 11:40 ` Jan Engelhardt
2007-05-04 12:30 ` WANG Cong
2007-05-04 13:53 ` la deng
2007-05-04 14:15 ` Jan Engelhardt
2007-05-05 6:37 ` la deng
2007-05-04 15:27 ` WANG Cong
2007-05-05 7:29 ` la deng
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=99e4df080705040132m41116db3y50c73c79528d6206@mail.gmail.com \
--to=ladeng.mimi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®