Alle 09:06, sabato 17 settembre 2005, Steven M. Schweda ha scritto: > I suppose that it's a waste of time and space to point this out here, > but native VMS status codes include a severity field (the low three > bits), with popular values being (from STSDEF.H): > > #define STS$K_WARNING 0 /* WARNING > */ #define STS$K_SUCCESS 1 /* SUCCESSFUL COMPLETION > */ #define STS$K_ERROR 2 /* ERROR > */ #define STS$K_INFO 3 /* INFORMATION > */ #define STS$K_SEVERE 4 /* SEVERE ERROR > */ > > Note that success (including informational) is odd, while anything worse > is even. > > While an OS like UNIX is handicapped by not having such a useful > convention, it would make sense for Wget to have status values which > distinguish among degrees of success and failure, like the ones > suggested by Hrvoje Niksic.
yes, i think it's a good idea. > Ideally, the values used could be defined in some central location, > allowing convenient replacement with suitable VMS-specific values when > the time comes. (Naturally, _all_ exit() calls and/or return statements > should use one of the pre-defined values.) mmh, i don't understand why we should use VMS-specific values in wget. > And, as long as I'm wasting time and space, I'll note that I'd still > like to see my VMS-related (and other) changes integrated into the main > Wget code stream. the wget code is going through a major refactoring effort. later on, just before releasing wget 2.0, i promise i will re-evaluate your patches and merge them if they're not too intrusive. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng. http://www.ing.unife.it GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linux http://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
