From: "Jay Krell" <jay.krell@cornell.edu>
To: "swe sd" <ccwork@hotmail.com>
Cc: <cygwin@sourceware.cygnus.com>
Subject: Re: problem in C++ pointer
Date: Sun, 12 Mar 2000 19:51:00 -0000 [thread overview]
Message-ID: <002901bf8c9f$cef9f680$0201a8c0@jayk_home4nt> (raw)
>I just wonder what is the different between the original code
>(using a single "cout", see test.cc attached) and new code
>(use another cout to print ++X[0], above).
The difference is that there is definitely a "sequence point" at every
semicolon. The effects of code to the left of a semicolon are guaranteed to
be visible before the effects of code to the right of the same semicolon.
int i, j, k;
F(j = i++, k = i++);
is undefined, the parameters can be evaluated in any order even sort of
simultaneously, whereas
j = i++;
k = i++;
F(j, k);
and
k = i++;
j = i++;
F(j, k);
are defined. The first line must be completely executed before the second
line.
> Actually, I tried the original program many time on my PC
>running Cygnus. To remove external factor, I close all other
>program after a re-boot.
I got the same behavior as you, with 2.95.2 to as well. I tried reading the
assembly (gcc -s x.cpp, then look at the file x.s) but it didn't include
commented out C++ source so was too hard to follow.
- Jay
-----Original Message-----
From: swe sd <ccwork@hotmail.com>
To: jay.krell@cornell.edu <jay.krell@cornell.edu>
Cc: cygwin@sourceware.cygnus.com <cygwin@sourceware.cygnus.com>
Date: Sunday, March 12, 2000 7:52 AM
Subject: Re: problem in C++ pointer
> First of all, thanks for you kindy answer ...
> I have the last question. I rewrite the program as follow:
> line 1: #include <iostream>
> line 2: void main()
> line 3: { const int size=10;
> line 4: int A[size];
> line 5: int *X=NULL, i;
> line 6: for (i=0;i<size;i++) A[i]=i;
> line 7: cout<<A[0]<<" "<<&A<<" "<<&A[0]<<endl;
> line 8: X=A;
> line 9: cout<<A[0]<<" "<<&A<<" "<<&A[0]<<endl
> line 10: <<*X<<endl
> line 11: <<*X+5<<endl
> line 12: <<*X<<" "<<A[0]<<endl
> line 13: <<5+X[0]<<endl
> line 14: <<( X[0]==0 ? "X[0]=0" : "X[0]!=0")<<endl;
> line 15: cout<<++X[0]<<endl; //the change here
> line 16: }
> and executing it gives output:
> $./a.out
> 0 0x259fd7c 0x259fd7c
> 0 0x259fd7c 0x259fd7c
> 0
> 5
> 0 0
> 5
> X[0]=0
> 1
> Obviously, it gives the correct answer (line 7 = line 9). I
>just wonder what is the different between the original code (using
>a single "cout", see test.cc attached) and new code (use another
>cout to print ++X[0], above).
> Actually, I tried the original program many time on my PC
>running Cygnus. To remove external factor, I close all other
>program after a re-boot. But the result is still wrong (see last e-mail).
> Then, to test my program is correct or not, I tried it on a
>UNIX SVR with gcc compiler. Then the program works properly.
> So, I just conclude there is some wrong with the cygwin, or
>not as good as gcc. Thanks.
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-03-12 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-12 19:51 Jay Krell [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-17 13:26 Heribert Dahms
2000-03-17 13:15 Jay Krell
2000-03-17 9:48 Jay Krell
2000-03-16 8:39 James Stern
2000-03-13 2:07 Jay Krell
2000-03-13 1:54 Bernard Dautrevaux
2000-03-12 7:52 swe sd
2000-03-12 0:06 Jay Krell
2000-03-11 21:20 swe sd
2000-03-11 16:33 Jay Krell
2000-03-11 16:29 Jay Krell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901bf8c9f$cef9f680$0201a8c0@jayk_home4nt' \
--to=jay.krell@cornell.edu \
--cc=ccwork@hotmail.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).