Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!umd5!brl-adm!adm!TLIMONCE%DREW.BITNET@CUNYVM.CUNY.EDU From: TLIMONCE%DREW.BITNET@CUNYVM.CUNY.EDU Newsgroups: comp.lang.c Subject: You win. (I now dis-like NOALIAS) Message-ID: <10989@brl-adm.ARPA> Date: 24 Dec 87 06:15:30 GMT Sender: news@brl-adm.ARPA Lines: 38 After reading all the recent posts about noalias I have come to the following conclusions: - Leave it out. It's not worth all this debating. - Leave it out of the standard. If someone wants to write an optimizer that would require it they will add it and it will create some prior art for the next revision. (actually, I like that person's idea about computing where it is needed and think that it can be done) ----- Why would someone want to include a \000 in the middle of a string? I've seen a pull-down menu routine (was it in DDJ?) that had something like: foo(3,"MenuItem1\000MenuItem2\000MenuItem3"); (or maybe that was in a structure?) This allowed the progammer to specify the text for each item in the menu easily. This has advantages over variable # of parameters (a bit easier to code). I prefer: foo("Thing1\000Thing2\000Thing3\000\000"); It's more like an empty-string terminated list of strings (a "null terminated null terminated string" perhaps?) ----- Someone made a comment about a typo of mine. Please, I do most of my net-ing late at night and proofing is difficult at 2AM. I suggest something better than const, register and noalias: "violet:" -- "I was blue when I wrote this code." (sorry) ____________________________________________________________________ ! Real World: Tom Limoncelli Computer World: ! ! Drew University BITNET: tlimonce@drew ! ! Box 1060 /--------------------------------------! ! Madison, NJ 07940 / Disclaimer: These are exclusively my ! !=======================\< opinions. That's the only thing ! ! Season's Greatings \\ my boss and I can agree about. ! !========================/ \---------------------------------------!