Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.lang.c Subject: Re: va_list used inMessage-ID: <10779@smoke.BRL.MIL> Date: 19 Aug 89 04:59:55 GMT References: <1140@midgard.Midgard.MN.ORG> <10720@smoke.BRL.MIL> <2095@dataio.Data-IO.COM> <10739@smoke.BRL.MIL> <13572@bloom-beacon.MIT.EDU> <10766@smoke.BRL.MIL> <1989Aug18.184635.26773@utzoo.uucp> Reply-To: gwyn@brl.arpa (Doug Gwyn) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 10 In article <1989Aug18.184635.26773@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: >How about a summary, Doug? Many of us thought JCLT was interesting until >we saw the price tag, at which point we said "forget it". Me too. However, if somebody is seriously trying to implement the C standard, a subscription to the JCLT may quickly pay for itself. I don't think I should attempt a summary of Sue's article; suffice it to say that it explained how H-P decided to deal with name-space issues in their ANSI C implementation.