apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 24325] apr_reslist doesn't work without threads
Date Sat, 26 Jul 2008 22:51:20 GMT

--- Comment #8 from Sönke Tesch <st@kino-fahrplan.de>  2008-07-26 15:51:19 PST ---
Guess I should make something clear: This suggestion is, at it's heart, _not_
about "using reslist when there are no threads", it's about preventing people
from (accidentally) doing so - and running into cryptic compiler errors.
The only reason I brought up enabling apr_reslist in a non-threaded environment
was to get a straight-forward interface, so the developer doesn't need to care
about OS details; if no threads, apr_reslist transparently drops all the
mumbo-jumbo. But I'm fine with a simple note, too, no need to argue about
apr_reslist's use, or the lack thereof, without threads.

Now, I do see that #error causes more harm than good, yet, and ironically, by
claiming that those including apr_reslist even though there's no thread support
might be annoyed even by a short #warning, you're now actually defending what
you say should not be done in the first place.

I'd still say there should be a warning in order to push good coding style, and
it wouldn't come out of nowhere if written clearly (that's the whole idea
anyway, to make something clear), but do as you believe.

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org

View raw message