home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!charnel!sifon!thunder.mcrcim.mcgill.edu!mouse
- From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
- Newsgroups: comp.lang.c
- Subject: Re: Question to test general C knowledge
- Message-ID: <1992Dec12.224541.29854@thunder.mcrcim.mcgill.edu>
- Date: 12 Dec 92 22:45:41 GMT
- References: <19980@ksr.com> <PTmLVB4w165w@quest.UUCP> <1992Dec11.175620.20308@crd.ge.com>
- Organization: McGill Research Centre for Intelligent Machines
- Lines: 19
-
- In article <1992Dec11.175620.20308@crd.ge.com>, volpe@bart.NoSubdomain.NoDomain (Christopher R Volpe) writes:
- > In article <PTmLVB4w165w@quest.UUCP>, kdq@quest.UUCP (Kevin D. Quitt) writes:
- >> jfw@ksr.com (John F. Woods) writes:
-
- >>> int i = 2;
- >>> i = ++i;
- >> If they say other than "it's undefined", *then* don't hire them.
- > This is an interesting question. Is the value of I really being
- > modified more than once? There are two assignment operations going
- > on, true. But, does assigning a variable the value that it already
- > has constitute a modification?
-
- It may not have that value yet, if the increment side-effect is
- deferred.
-
- der Mouse
-
- mouse@larry.mcrcim.mcgill.edu
-