X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <1cbe225f0704160234u24b104a5o9b459178e895a5a8 AT mail DOT gmail DOT com> <018901c7800b$5c4ec450$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <4623592C DOT 2000905 AT sh DOT cvut DOT cz> <019c01c7801a$6db51f00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <7231C15EAC2F164CA6DC326D97493C8B01FA0655 AT exchange35 DOT fed DOT cclrc DOT ac DOT uk> Subject: RE: C++ name with leading underscore character not Compiling Date: Mon, 16 Apr 2007 12:53:50 +0100 Message-ID: <01a001c7801d$e5d16220$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <7231C15EAC2F164CA6DC326D97493C8B01FA0655@exchange35.fed.cclrc.ac.uk> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 16 April 2007 12:50, Adye, TJ (Tim) wrote: > This means that a single leading underscore is fine in local scope, as > long as it is not followed by an uppercase letter (I am only aware of > conflicts with a single upper-case character (eg. _L), but I think the > standard would also prevent _Local). > > So, the case here ("_name" as an argument name) should be fine. Except that that was just an example, and in fact a misleading one, because what Chelton's code was /actually/ using was "_N"... hence the problem. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/