kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mohit89mlnc@gmail.com (mohit verma)
To: kernelnewbies@lists.kernelnewbies.org
Subject: why only C?
Date: Mon, 4 Apr 2011 00:47:47 +0530	[thread overview]
Message-ID: <BANLkTikEmyURpOLS7DEvxsT6HEOPRg-ucg@mail.gmail.com> (raw)

Hi list,

I have a very basic question.

As far as i can decipher , we impose Object oriented paradigm in kernel
space using C  : like using gates to allow only one way entry and binding
functions to structures in a OOP fashion  and trying to make them private to
that structure only  , encapsulation of one struct into another structure
(and lots of features ) and itself  lots of kernel subsystem supports like
driver interface and blah blah behaving like **objects** .......

why dont we use some fully OOPs supportive language like JAVA or partial
supportive language like  C++ to construct Linux Kernel????

I don't  think that performance is the main reason behind all this . Is it??

Thanks a lot in advance.



-- 
........................
*MOHIT VERMA*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110404/269fd7c5/attachment.html 

             reply	other threads:[~2011-04-03 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 19:17 mohit verma [this message]
2011-04-03 19:23 ` why only C? Anuz Pratap Singh Tomar
2011-04-03 19:25 ` Daniel Baluta
2011-04-03 19:49 ` Bernd Petrovitsch
2011-04-04  0:30   ` Chaitannya Mahatme
2011-04-04  9:58     ` Bernd Petrovitsch
2011-04-04  9:04   ` mohit verma
2011-04-06 17:37 ` StephanT
2011-04-06 19:30   ` mohit verma

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=BANLkTikEmyURpOLS7DEvxsT6HEOPRg-ucg@mail.gmail.com \
    --to=mohit89mlnc@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).