mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Olivier Cornu" <o.cornu@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: What would your perfect language for Linux development look like?
Date: Fri, 28 Mar 2008 18:52:14 +0100	[thread overview]
Message-ID: <7b4bf7ff0803281052j3e5d57c9xf6d1f308c9d9cdb9@mail.gmail.com> (raw)

Hello everybody,

I've recently started a toy project: a programming language aimed at
OS development only.
It's nothing revolutionary really and it will very likely never be
used by anyone - except perhaps me: the main intent is to learn more
about programming languages and OS specific needs in this regard (the
idea grew while playing with Linux and Minix C sources and reading
about OS design issues).

I would be glad to hear you share your experience about C as a
programming language in OS development context, like:
- what missing feature would you like C to have?
- what feature should be removed?
- what kind of language cleanup would you like to see?
In other words, what would your perfect language for Linux development
look like?

Regards,
Olivier

             reply	other threads:[~2008-03-28 17:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 17:52 Olivier Cornu [this message]
2008-03-28 18:22 ` bart.vanassche

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=7b4bf7ff0803281052j3e5d57c9xf6d1f308c9d9cdb9@mail.gmail.com \
    --to=o.cornu@gmail.com \
    --cc=linux-kernel@vger.kernel.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®