From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: "Douglas A. Gwyn" Message-ID: <3DD43567.99F5F825@null.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <200211141857.SAA01742@localhost.localdomain> Subject: Re: [9fans] how to avoid a memset() optimization Date: Fri, 15 Nov 2002 10:51:06 +0000 Topicbox-Message-UUID: 213cf484-eacb-11e9-9e20-41e7f4b1d025 Steve's reponse was very nice. Another way of putting it is that the "right" behavior is not at all obvious once you think hard enough about it and examine a wide enough variety of platforms and application requirements. One of the tasks undertaken by the C standards committee was to negotiate among the conflicting demands and to draw the line somewhere. Individuals would very likely draw the line in other places, depending on their personal prejudices and values. If the existing standard specification is causing significant real problems, there is a mechanism in place to get it reconsidered and maybe the official line could be redrawn. The really important thing is to understand where the official line *is* and to observe it (on both sides, programmer and implementor); that allows all parties to work together even if they all still want to grumble about some aspect of the work..