From -5562114740512115732 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,74637d148a591f02 X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 2001-04-02 10:02:05 PST Return-Path: X-Authentication-Warning: mulga.cs.mu.OZ.AU: fjh set sender to devnull@stump.algebra.com using -f Path: supernews.google.com!sn-xit-03!supernews.com!logbridge.uoregon.edu!newsfeed.stanford.edu!comp-std-cpp-robomod!not-for-mail X-Robomod: STUMP, ichudov@algebra.com (Igor Chudov) Message-ID: <4ZvL68C9O6x6Ew$F@ntlworld.com> From: Francis Glassborow Reply-To: Francis Glassborow Newsgroups: comp.std.c++ Subject: Re: Proposal: two real uses for the "auto" keyword References: <052201c0b4ab$603e8050$0500a8c0@dragonsys.com> <0ul4ct4hd6si29tea3cjr81kpjdvhoe8gi@4ax.com> Organization: Southfield Microcomputer SS MIME-Version: 1.0 X-Newsreader: Turnpike Integrated Version 5.00 U Approved: Fergus Henderson , moderator of comp.std.c++ Date: Mon, 2 Apr 2001 11:57:46 CST Lines: 33 Xref: supernews.google.com comp.std.c++:4109 In article , Vladimir Prus writes >Second, it seems to me that 'auto' is little misleading. Better name would >be 'infered', according to functional programming terms. But we have to be very careful about introducing new keywords. However at a recent BSI C++ Standards Panel meeting (held in an Oxford hostelry, which may be significant) we realised that we have a whole raft of potential keywords that will not possibly break existing code. Consider: #include using namespace std; ~using std::sort; Do I even need to explain what such code would do? :) And think how useful a ~using directive would be to undo the damage caused by an idiot programmer who has used using directives inappropriately. -- Francis Glassborow See http://www.accu.org for details of The ACCU Spring Conference, 2001 (includes many regular participants to C & C++ newsgroups) --- [ 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 ]