From 2591758693170860687 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,ccbfcafab96cf493 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2001-11-27 15:07:01 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!dispose.news.demon.net!news.demon.co.uk!demon!mail2news.demon.co.uk!not-for-mail From: brangdon@cix.co.uk (Dave Harris) Newsgroups: comp.std.c++ Subject: Re: Proposol to increase robustness of programs Date: Tue, 27 Nov 2001 23:05:57 GMT Approved: Fergus Henderson , moderator of comp.std.c++ Message-ID: References: <3C03E02E.FA9754A3@acm.org> Reply-To: brangdon@cix.co.uk X-Trace: mail2news.demon.co.uk 1006902362 mail2news:1322 mail2news mail2news.demon.co.uk X-Complaints-To: abuse@demon.net X-Mail2News-Path: news.demon.net!mulga.cs.mu.oz.au X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) X-Orig-NNTP-Posting-Host: host213-120-17-206.webport.bt.net (213.120.17.206) X-Orig-X-Trace: fu-berlin.de 1006902207 5765510 213.120.17.206 (16 [57443]) Lines: 19 Xref: archiver1.google.com comp.std.c++:8325 petebecker@acm.org (Pete Becker) wrote (abridged): > Obviously, when you get an upgraded library you check the documentation > to see if any of the changes affect your code. I would welcome a tool to automate the checking. It is very error-prone to do it manually. And I think it's better to put this kind of consistency check into the compiler than to have a separate Lint-like utility. Dave Harris, Nottingham, UK | "Weave a circle round him thrice, brangdon@cix.co.uk | And close your eyes with holy dread, | For he on honey dew hath fed http://www.bhresearch.co.uk/ | And drunk the milk of Paradise." --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.research.att.com/~austern/csc/faq.html ]