Advanced Minds

  • Decrease font size
  • Default font size
  • Increase font size
  • default color
  • red color
  • green color
FireBoard
Welcome, Guest
Please Login or Register.    Lost Password?
c++ precedence Precedence in C and C++ (1 viewing) (1) Guests
Go to bottom Post Reply Favoured: 0
TOPIC: c++ precedence Precedence in C and C++
#8280
Andrew Koenig (Visitor)
Click here to see the profile of this user
Birthdate:
c++ precedence Precedence in C and C++  
Imanpreet Andrew Koenig < This e-mail address is being protected from spam bots, you need JavaScript enabled to view it wrote in message <news: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it Imanpreet {int x = 5, *y = &x; y
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#8281
Jukka Liimatta (Visitor)
Click here to see the profile of this user
Birthdate:
c++ precedence Precedence in C and C++  
translating a C++ program Yes, but that's out-of-context, I tried to emphasis the fact that the order you perform operations DOES matter as far as the datatype is concerned, I gave much better example in a follow-up to the thread. When we express our desire in C++, we expect the resulting instruction stream to carry that intent in binary. The out-of-order execution was just my way of saying, that, sure, the order of operations actually done in hardware is a different thing. How can you keep repeating that we somehow disagree when we do not? =) Jukka
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#8282
Ioannis Vranos (Visitor)
Click here to see the profile of this user
Birthdate:
c++ precedence Precedence in C and C++  
include <iostream int main() {int x = 5, *y = &x; y
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#8283
c++ precedence Precedence in C and C++  
Imanpreet Andrew Koenig < This e-mail address is being protected from spam bots, you need JavaScript enabled to view it wrote in message <news: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it Imanpreet {int x = 5, *y = &x; y
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#8284
Ioannis Vranos (Visitor)
Click here to see the profile of this user
Birthdate:
c++ precedence Precedence in C and C++  
int main() { int x=5, *y = &x , **z = &y;
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#8285
Ioannis Vranos (Visitor)
Click here to see the profile of this user
Birthdate:
c++ precedence Precedence in C and C++  
Ioannis Vranos <noicys@no_.yahoo.s_pam.com wrote in message I was wrong in both situations concerning that the pointers pointed at wrong memory places at the end, but i am right on the fact that you point twice in illegal areas which is not guaranteed to work. Only one element past the end of an array is safe to point, and there only to point, not to dereference (for standard library containers the same applies too). Ioannis
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop
darmowe smocze monety w metin 2 rinnegan obozy młodzieżowe straż pożarna gry dziewiarstwo
songs guitar internet crazy car loans