lkml.org 
[lkml]   [2006]   [Apr]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Compiling C++ modules
Michael Poole wrote:
>> How many of these leave something out? how much time is spent
>> deciphering the code when something goes wrong, or is even suspected?
>>
>
> Probably fewer cases and less time than you suspect, respectively.
> Just as C++ gives you tools, C does too, but far more important than
> language tools is the discipline used when writing code: discipline to
> think through the code, to structure it rationally, and to reuse the
> rational structures that others have devised in the past. C++ gives
> you well-tested helper classes to manage object locking. Linux gives
> you its own well-tested examples of known and tried design patterns.
>
I agree. It certainly helps when you first write the code. But it's
still difficult to read and modify the code. And I'd prefer to see the
effort involved in coding to these patterns and in enforcing them used
to other purposes.

I also suspect drivers are written with less rigor.

--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-04-25 21:16    [W:0.153 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site