Re: Privilege-escalation attacks on NT-based Windows are unfixable

From: Edward Elliott (nobody@127.0.0.1)
Date: 08/23/02


From: Edward Elliott <nobody@127.0.0.1>
Date: Fri, 23 Aug 2002 20:33:58 GMT

Barry Margolin wrote:
> by contract. Many programmers rebel against being forced into a
> straightjacket by B&D languages like this. Unfortunately, when they use a
> language that gives them lots of rope, they tend to hang themselves with
> it.
>
> You can't have it both ways: demanding a simple, flexible language, and
> then complaining that it doesn't protect you from all your mistakes. C

No but I think C++ is a great compromise. If you stick to standard
containers like string, vector, map, etc and utility classes like smart
pointers, you can eliminate a large number of programming mistakes. Not
only that, but these classes are more useful than their raw counterparts
as well.

IMO the problem is programming is not taught as an engineering
discipline. If you're building a bridge and you need a span or a
support or something, you choose from a small set of tried-and-true
designs. You rarely deviate into designing your own building blocks,
and when you do you have a damn good reason for doing so. Programming
should be the same way; 99% of programs should never touch a raw pointer
(at the application code level, anyway).

> But unless you switch to C++ and its bloated STL, you're stuck with many of
> C's fundamental design limitations.

There's no reason to call the STL bloated. It provides a vast array of
useful utilities with little overlap. Execution speed is entirely a
function of implementation. There are extremely fast STL
implementations out there; see www.stlport.org for one.

-- 
Edward Elliott



Relevant Pages

  • Re: object system...
    ... for that you need machine language. ... isn't even as fast as other systems programming languages. ... Stroustrup's stated design goal was to enable ... all manner of elegance or abstraction can be sacrificed for speed, ...
    (comp.object)
  • Re: DirectX in HLA
    ... I guess that you have a great knowledge of DirectX ... > understanding by looking at them in assembly language... ... > actually represents, really, is a means to "undo" the OOP so ... > is NOT an "OOPL" (object-orientated programming language), ...
    (comp.lang.asm.x86)
  • Re: DirectX in HLA
    ... I guess that you have a great knowledge of DirectX ... > understanding by looking at them in assembly language... ... > actually represents, really, is a means to "undo" the OOP so ... > is NOT an "OOPL" (object-orientated programming language), ...
    (alt.lang.asm)
  • Re: LSP and subtype
    ... What is the class of problems solvable using UML? ... the language of physics cannot describe. ... whatever paradigm equivalent to 2GL/3GL ... there is still a great need for reuse and generic programming. ...
    (comp.object)
  • Re: Why C Is Not My Favourite Programming Language
    ... If you decide afterall that C programming is just not your thing you ... > C has no string type. ... > compiler take care of the rest. ... Why does any normal language ...
    (comp.lang.c)

Quantcast