Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: Kazutoshi Satoda Newsgroups: comp.std.c++ Subject: Re: Defect Report: Unclear wording about capacity of temporary buffers Date: Sun, 28 Aug 2011 08:41:17 -0700 (PDT) Organization: unknown Lines: 46 Sender: std-cpp-request@vandevoorde.com Approved: james.dennett@gmail.com Message-ID: <4E58F6CA.5080306@f2.dion.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed X-Trace: news.albasani.net tmOF+FWa9ox5qdHAQm4riprwQOj/gOT/J67JxsvfIKvzTj1tJtCGJbPIl4FkdVbpuDrG4lr71ZEiPpuDktTkXA== NNTP-Posting-Date: Sun, 28 Aug 2011 15:41:18 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="24gaBlPjAG0xSZtGZinasHWVQmvhwsgsYsp29YwBpAlfiIK5jeLAZbO9AX2GgQKV6Izm9sxu+GKFb40GrjFTqwtBv7S3OKXJw9Tq7nGbFjUDnUH0OE04dyMECG7GjTZm"; mail-complaints-to="abuse@albasani.net" X-Mailer: Perl5 Mail::Internet v2.05 X-Submission-Address: std-cpp-submit@vandevoorde.com Cancel-Lock: sha1:WzDlRqdHhJPF3qfLZKiD5iHbw7E= X-Original-Date: Sat, 27 Aug 2011 22:53:14 +0900 Xref: x330-a1.tempe.blueboxinc.net comp.std.c++:260 Daniel Krügler wrote: > > If at all this looks more like an editorial problem to me, no real > defect in the wording. What is the difference of "editorial problem" and "real defect" ? AFAIK, all problem reports about standard are collectively treated "Defect Report". Thus I believe this problem (unclear wording) is a defect. http://www.comeaucomputing.com/csc/faq.html#B13 If I should report "editorial problem" in other way, please explain what is it and how to report it. > I also believe that the suggested form "having > up to n capacity" is bad English. Sorry but, I'm not a native English speaker and I'm not sure how bad the wording was. However, here is another try. I hope the editors in standard committee will give better wording if it is still bad. Complete ignorance of my wording is also OK for me if the original intent was clarified in the standard. Proposed resolution: Change 20.6.11 [temporary.buffer] paragraph 1 and 2 to Effects: Obtains a pointer to storage whose capacity (number of adjacent T objects storable in it) is up to n. It is implementation defined whether over-aligned types are supported (3.11). Returns: A pair containing the buffer's address and capacity (in the units of sizeof(T)), or a pair of 0 values if no storage can be obtained or if n <= 0. -- k_satoda [ comp.std.c++ is moderated. To submit articles, try posting with your ] [ newsreader. If that fails, use mailto:std-cpp-submit@vandevoorde.com ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.comeaucomputing.com/csc/faq.html ]