All of lore.kernel.org
 help / color / mirror / Atom feed
From: WANG Cong <xiyou.wangcong@gmail.com>
To: la deng <ladeng.mimi@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: c 's OOP in VFS vs c++'s OOP
Date: Fri, 4 May 2007 23:27:52 +0800	[thread overview]
Message-ID: <20070504152752.GB4258@localhost.localdomain> (raw)
In-Reply-To: <99e4df080705040653l38daa61aw3883b7c55c8e9de7@mail.gmail.com>

On Fri, May 04, 2007 at 09:53:34PM +0800, la deng wrote:
>On 5/4/07, WANG Cong <xiyou.wangcong@gmail.com> wrote:
>>On Fri, May 04, 2007 at 01:40:04PM +0200, Jan Engelhardt wrote:
>>>
>>>On May 4 2007 19:00, la deng wrote:
>>>>
>>>>
>>
>>C gives you the power to control nearly everything. You can, of course, 
>>control the registers via inserting assembly code. That's not the fault of 
>>C.
>I think you don't understand me correctly
>
>I know c can inline assmebly to control registers
>
>but,this control not the globe Analysis of control register like
>internal of c++ compiler or lisp 's compiler language,c can't
>
>sigh

You didn't understand me correctly.

I mean that C gives you the power to control them, you can do analysis and then do what you like. It's up to you. But I think if you add optimizing options, the compiler won't be so foolish as what you say.

So, can we stop now?


  parent reply	other threads:[~2007-05-04 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04  8:32 c 's OOP in VFS vs c++'s OOP la deng
     [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 [this message]
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=20070504152752.GB4258@localhost.localdomain \
    --to=xiyou.wangcong@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=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 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.