Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 6784 invoked by uid 6000); 23 Nov 1999 23:33:52 -0000 Received: (qmail 6638 invoked from network); 23 Nov 1999 23:33:45 -0000 Received: from postoffice.princeton.edu (HELO Princeton.EDU) (128.112.129.120) by taz.hyperreal.org with SMTP; 23 Nov 1999 23:33:45 -0000 Received: from mailserver.Princeton.EDU (mailserver.Princeton.EDU [128.112.129.65]) by Princeton.EDU (8.9.3/8.9.3) with ESMTP id SAA19231 for ; Tue, 23 Nov 1999 18:33:43 -0500 (EST) Received: from princeton.edu (zedlwski.student.Princeton.EDU [140.180.153.22]) by mailserver.Princeton.EDU (8.9.3/8.9.3) with ESMTP id SAA00973 for ; Tue, 23 Nov 1999 18:33:43 -0500 (EST) Message-ID: <383B242E.9D8515C2@princeton.edu> Date: Tue, 23 Nov 1999 18:33:02 -0500 From: John Zedlewski X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.13-4mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: C++ reserved words References: <4.2.0.58.19991123174603.00e9ac10@pop.ma.ultranet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Personally, I always have my editor set to syntax highlight for C++. Any variables that use reserved words look funny immediately. --JRZ > For people not familiar with C++, you might want to watch out for > these reserved words if there is any chance your code will be > converted to C++ (some of these are very unlikely to appear anywhere > but in a C++ program, but you never know): bad_cast, bad_typeid, > bool, catch, class, const_cast, delete, dynamic_cast, explicit, > export, false, friend, inline, mutable, namespace, new, operator, > private, protected, public, reinterpret_cast, static_cast, template, > this, throw, true, try, typeid, typename, using, virtual.