Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!van-bc!robinson
Newsgroups: comp.lang.c
Subject: Re: #define DEBUG... (using printf for debugging)
Message-ID: <1990May9.003253.3637@mdivax1.uucp>
Date: 9 May 90 00:32:53 GMT
References: <11290@hoptoad.uucp> <40628@cornell.UUCP> <801@oz.rci.dk> <1990May8.183211.2661@mdivax1.uucp> <12814@smoke.BRL.MIL>
Reply-To: mdivax1!robinson (Jim Robinson)
Organization: Mobile Data International, Richmond, B.C., Canada
Lines: 15
Return-Path: <mdivax1!robinson>
Apparently-To: van-bc!rnews

In article <12814@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
>In article <1990May8.183211.2661@mdivax1.uucp> mdivax1!robinson (Jim Robinson) writes:
>>Isn't the use of __LINE__ non-portable?
>
>I guess it depends on your definition of portable.
>The C standard requires that __LINE__ be supported by every conforming
>implementation.

Is this the ANSI C Standard? An admittedly cursory look thru a copy of the
K&R C manual (first edition) did not produce any mention of __LINE__.

And, is __FILE__ required to be supported?
-- 
Jim Robinson
{uunet,ubc-cs}!van-bc!mdivax1!robinson