All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Giovanni A. Orlando" <gorlando@futuretg.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Marc-André Laverdière" <ma_laver@ciise.concordia.ca>,
	reiserfs-list@namesys.com
Subject: Re: Coding Standards
Date: Fri, 03 Mar 2006 17:11:50 -0400	[thread overview]
Message-ID: <4408B116.9090801@futuretg.com> (raw)
In-Reply-To: <44087B43.4000900@namesys.com>


>>Hello,
>>
>>I was reading an article long ago where Mr Reiser was saying that he
>>was using military grade coding standards. And that it is also the
>>reason why Reiser4 is not integrated by default in the Linux kernel.
>>    
>>
>
>I think that was a minor issue.  The major issues are political.
>
>  
>
So ... what the hell happens? Why is not included yet?

Thanks,
Giovanni.

>>My experience at looking at GNU code is that it is sloppy and I want
>>to start a high-assurance project with the best of the best of coding
>>practices... something making me feel that the GNU coding guidelines
>>are not the best of options.
>>    
>>
>
>I would really look into the various security and secure coding papers
>and articles that have been funded by DARPA and others over the years. 
>Pick through them, read them, and code that way.  The guys writing the
>articles are much more expert than I am on it.
>
>  
>
>>Your input would be very appreciated!
>>
>>    
>>
>
>  
>


-- 

--
--
http://www.FutureTG.com      - The Main Website.
http://www.FTLinuxCourse.com - The Website for Linux Training.
http://www.RPMParadaise.com  - The Website for RPM Packages.

Phone: +58 412 55 41 338 (I am in Caracas, actually)

FT Addresses are located at: http://www.futuretg.com/FT/contact.html


  reply	other threads:[~2006-03-03 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 22:45 Coding Standards Marc-André Laverdière
2006-03-03 17:22 ` Hans Reiser
2006-03-03 21:11   ` Giovanni A. Orlando [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-30 18:29 coding standards Linda
2015-03-30 18:52 ` Wei Liu
2015-03-30 19:26   ` Linda Jacobson
2015-04-02 13:15     ` Lars Kurth

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=4408B116.9090801@futuretg.com \
    --to=gorlando@futuretg.com \
    --cc=ma_laver@ciise.concordia.ca \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    /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.