Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!uhura.cc.rochester.edu!ur-valhalla!micropen!dave
From: dave@micropen (David F. Carlson)
Newsgroups: comp.lang.c
Subject: Re: printf() problem
Summary: not quite right...
Keywords: C printf
Message-ID: <679@micropen>
Date: 27 Apr 89 14:21:51 GMT
References: <11657@hodge.UUCP> <89Apr26.092233edt.18850@me.utoronto.ca>
Organization: Micropen Dirent Writing Systems, Pittsford, NY
Lines: 22

In article <89Apr26.092233edt.18850@me.utoronto.ca>, zougas@me.utoronto.ca ("Athanasios(Tom) Zougas") writes:
! In article <11657@hodge.UUCP> jdm@hodge.UUCP (jdm) writes:
! >
! >    Perhaps someone could explain this printf() phenomena to me.
! >
! >    This happens in both Turbo C 2.0 and MS C 5.1.
! 
! It would happen in any C.
! 
! 	tom zougas

Well, actually it *can* happen in any C.  If it did happen in every C then
order of evaluation of function parameters *would* be guaranteed, wouldn't it?!

1/2 :-)


-- 
David F. Carlson, Micropen, Inc.
micropen!dave@ee.rochester.edu

"The faster I go, the behinder I get." --Lewis Carroll