From: stman937-linewbie@yahoo.com (StephanT)
To: kernelnewbies@lists.kernelnewbies.org
Subject: why only C?
Date: Wed, 6 Apr 2011 10:37:22 -0700 (PDT) [thread overview]
Message-ID: <906786.47540.qm@web30802.mail.mud.yahoo.com> (raw)
In-Reply-To: <BANLkTikEmyURpOLS7DEvxsT6HEOPRg-ucg@mail.gmail.com>
>why dont we use some fully OOPs supportive language like JAVA or partial
>supportive language like C++ to construct Linux Kernel????
Hi Mohit,
This is an old debate, which by the way extends to the whole embedded realm,
not only to Linux. The best way to get an acceptable answer and understanding
to your question is to do some work by yourself.
Start by writing a very basic scheduler for some embedded platform. You may use
even your PC for this. Consider two tasks, one writing "A" and the other "B" to
the console. Read "Just for Fun: The Story of an Accidental Revolutionary" by
Linus Torvalds and David Diamond. Linus explains in grand detail how this can
be done on your PC.
Once you got it in "C" start again and write it in "C++" and why not in "Java".
And when you done with all this exercise, please come back here and publish
your code and conclusions. Everybody and especially you will have to learn
from this experiment. At my knowledge it has not yet been done by anyone.
You may bind and lead a team of volunteers willing to participate to this
experiment. It will go faster. I really think this is the way to get a clearer
idea
about the best tools to write embedded software.
Best luck in this endeavor,
Stephan.
next prev parent reply other threads:[~2011-04-06 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 19:17 why only C? mohit verma
2011-04-03 19:23 ` 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 [this message]
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=906786.47540.qm@web30802.mail.mud.yahoo.com \
--to=stman937-linewbie@yahoo.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 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.