On Wed, Apr 12, 2000 at 01:36:43PM -0700, dean gaudet wrote:
> > If you mess up, things will break the second you populate /proc.
>
> hmm, how is that? there's no type checking, you could easily store an
> integer where a string is expected.
Very true. You might get into problems if you have more %'s than arguments
perhaps.
> is my point making any more sense yet? :) printf/scanf are total special
> cases and gcc supports them. it's a generally bad style of programming
> though whose only saving grace is that it can produce small code. hence
> my original question.
What you lose is:
* some type checking
What you gain:
* less code that can contain errors
* any errors are quickly discovered
('reading from /proc/sys/net/blah/blah gives garbage/crashes
my kernel')
* any errors are quickly diagnosed (only 1 line where they can be)
It's a bit like putting all your eggs in one basket. This makes sense if you
gave a really good basket.
Regards,
bert hubert.
--
| http://www.rent-a-nerd.nl
| - U N I X -
| Inspice et cautus eris - D11T'95
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:19 EST