From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6844 invoked by alias); 23 Oct 2003 15:28:13 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 6836 invoked from network); 23 Oct 2003 15:28:12 -0000 Received: from unknown (HELO mail-srv2.micron.com) (137.201.242.130) by sources.redhat.com with SMTP; 23 Oct 2003 15:28:12 -0000 Received: from mail-srv2.micron.com (localhost [127.0.0.1]) by mail-srv2.micron.com (8.12.9/8.12.2) with ESMTP id h9NFSDwh027522 for ; Thu, 23 Oct 2003 09:28:14 -0600 (MDT) Received: from ntxboimbx07.micron.com (ntxboimbx07.micron.com [137.201.80.94]) by mail-srv2.micron.com (8.12.9/8.12.2) with ESMTP id h9NFSA0s027482; Thu, 23 Oct 2003 09:28:11 -0600 (MDT) From: lrtaylor@micron.com X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: How to suppress warning? Date: Thu, 23 Oct 2003 15:28:00 -0000 Message-ID: <363801FFD7B74240A329CEC3F7FE4CC4A277A5@ntxboimbx07.micron.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: To: , X-Scanned-By: MIMEDefang 2.37 X-SW-Source: 2003-10/txt/msg00360.txt.bz2 Why is it that the preprocessor and compiler can't just be smart enough to handle it? I might have expected something like this ten years ago, but it surprises me that it's not smarter now. Now, I'm sure it has to do with complications in the parser, but still... Lyle -----Original Message----- From: Eljay Love-Jensen [mailto:eljay@adobe.com]=20 Sent: Thursday, October 23, 2003 9:21 AM To: Lev Assinovsky; Gcc-Help (E-mail) Subject: RE: How to suppress warning? Hi Lev, Why I'm not surprised that the Windows' source files are malformed. :-) If I'm not mistaken, the newline-at-eof is required. Especially important for the preprocessor, such as a #endif at the end of the file (since the preprocessor is less forgiving), or when someone has a //-comment as the last line in the file. --Eljay