[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: assertions (a question of coding style)

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-09-15 16:52:33 CEST

Daniel Stenberg <daniel@haxx.se> writes:
> IMHO assert()s are good. Used properly they can be removed with (or without)
> the right #define and they can be used to simplify debugging.
> Then, you know, I'm not one of the "core guys"...

Thanks for the advice.

And, if I may risk sounding warm and fuzzy:

Being a "core guy" is merely a matter of this being a full-time job.
And/or a matter of having commit access, depending on how you want to
define "core". But whoever sends in a few good patches will have
commit access, because hey, why would we want to spend our time
applying patches that the author could just be committing directly?
So "core" is a pretty loose concept here. :-)

For what it's worth, many aspects of Subversion have been decisively
influenced by clueful people on this list posting their opinions. To
pick a random example, using XML for working copy adm files -- a
choice that only seems wiser with every line of code -- was suggested
by Scott Reedstrom. (This excellent idea hadn't even occurred to me
until he first mentioned it, in fact.)

So please don't discount your opinion just because you happen not to
be working on Subversion full time, or not committing directly to the
repository. When you say that your experience favors use of assert(),
we listen, and there's a good chance that assert() will be used more
often because of your input.

That's some responsibility for just posting to a list, eh? :-)

Received on Sat Oct 21 14:36:08 2006

This is an archived mail posted to the Subversion Dev mailing list.