Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!dhesi From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi) Newsgroups: comp.lang.c Subject: Re: In defense of the X3J11 committee Message-ID: <8160@bsu-cs.bsu.edu> Date: 10 Jul 89 20:48:40 GMT References: <225800176@uxe.cso.uiuc.edu> <11831@bloom-beacon.MIT.EDU> <10466@smoke.BRL.MIL> <18308@mimsy.UUCP> <10474@smoke.BRL.MIL> <1147@crdgw1.crd.ge.com> Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi) Organization: CS Dept, Ball St U, Muncie, Indiana Lines: 23 In article <1147@crdgw1.crd.ge.com> davidsen@crdos1.UUCP (bill davidsen) writes: >In article <10474@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes: >| ...so if one really didn't >| care enough about C standardization to make this investment worthwhile... >The cost for >regular and committee meetings was about 6 weeks time the first year, >and 9 the second. It gets worse if you care not only about C standardization, but also Ada standardization, Pascal standardization, Fortran standardization, etc. (Not to mention POSIX standardization, SVID standardization, RS-232 standardization, local housing code standardization, and so on.) I haven't even mentioned standardized high-resolution television, standardized digital audio tape, and standardized headlight switches on rented automobiles. Our lives are *full* of standards that affect us. Were any individual do all that he seems to be expected to do to influence standards he "cares" about, he would likely have no time for anything else. -- Rahul Dhesi UUCP: ...!{iuvax,pur-ee}!bsu-cs!dhesi