[openbeos] Re: Updating OSes bit by bit

> >c++ is the source of evil... procedural programming in this special case.
> >most of those bugs are buffer overflows or underflows which result in a
> >wrong usage of memory. as long as you rely on c++ as your main os
language
> >you will always confront those problems. a good framework can reduce the
> >problem but not extinct it.
> >i'm eager to see your good work though... but i'm more eager to fully
> >compile BeOS from scratch... BFS: BeOS From Scratch ^_^
>
> Are you refering to the OO way of development? .. hmm.. I wonder in what
> direction M$ is takin their system/api:s... =)

This sounds more like a language issue rather than OO methology.  Microsoft
is definitely moving more and more to object oriented.  Their API was
originally C.  It now has a C++ wrapper.  However, the current change is a
much bigger concern.  Since they came up with C# they've been making a C#
API and I do mean API not wrapper.  C# has significant advantages over C++
because it has list, string, and other such classes.  This makes buffer runs
and other common bugs impossible (except if it happens in the C# library).
C# doesn't completely eliminate pointers and other things that a programmer
could easily make a mistake with.  However, doing so will be very obvious
since you have to do that is a special way

risky_code // I can't remember the correct word for this
{
    // risky_code that uses pointers and other suspicious code
    // including calls to c/c++ and other things that are risky
}

I believe Microsoft has plains to rewrite there OS in C#.  I know they are
doing that for MS Office.

In short, Microsoft will have significantly more stable software soon and
we've got a lot of catching up to do.


Later,
Scott MacMaster



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.688 / Virus Database: 449 - Release Date: 5/18/2004

Other related posts: