• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Strange behavior in XCode, not exhibited in Dev-C++
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Strange behavior in XCode, not exhibited in Dev-C++


  • Subject: Re: Strange behavior in XCode, not exhibited in Dev-C++
  • From: Richard Rehl <email@hidden>
  • Date: Fri, 9 Feb 2007 12:29:51 -0500

Here's something weird - when passing double absoluteLargest, any value, to function findRootWidth, it always shows up as value 2.233392082528404e-308 at the start of the function.

If I enable #include <iostream> in the source file, the correct value shows up in the function.

Any more thoughts?

On Feb 9, 2007, at 10:15 AM, John Daniel wrote:

How are you compiling your code? Are you using g++ or gcc and adding your own c++ paths?

Here is what I have:
medusa:/tmp/stdtest jdaniel$ diff FindColWidths1.cpp FindColWidths2.cpp
3c3
< //#include <iostream> //........................Here is the line in question...........................
---
> #include <iostream> //........................Here is the line in question...........................
medusa:/tmp/stdtest jdaniel$ g++ -o run1 stdtest.cpp FindColWidths1.cpp
medusa:/tmp/stdtest jdaniel$ g++ -o run2 stdtest.cpp FindColWidths2.cpp
medusa:/tmp/stdtest jdaniel$ ./run1 > run1.txt
medusa:/tmp/stdtest jdaniel$ ./run2 > run2.txt
medusa:/tmp/stdtest jdaniel$ diff run1.txt run2.txt
medusa:/tmp/stdtest jdaniel$
medusa:/tmp/stdtest jdaniel$ diff run1 run2
Binary files run1 and run2 differ


This really makes no sense because this #include is not in the source file with the IO statements. It isn't needed in that file at all. There has got to be something else.

John

On Feb 9, 2007, at 6:30 AM, Richard Rehl wrote:

Well, I just dled and installed XCode 2.41, and the behavior has not gone away. Any more ideas?

On Feb 8, 2007, at 6:18 PM, John Daniel wrote:

Your behavior is not exhibited in my Xcode environment either. Which version of GCC are you using? What does gcc_select return on your machine? This is my output.

medusa:/tmp jdaniel$ gcc_select
Current default compiler:
gcc version 4.0.1 (Apple Computer, Inc. build 5363)

John

On Feb 8, 2007, at 4:33 PM, Richard Rehl wrote:

As you can guess, I'm not very experienced at this. I've had to get a POS PC for some coursework that I'm taking, so tried to compile the same project in Dev-C++. The above behavior is not exhibited in that environment, so I'm mystified. If anyone's interested, here's the code:


.



_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Strange behavior in XCode, not exhibited in Dev-C++
      • From: Richard Rehl <email@hidden>
References: 
 >Strange behavior in XCode, not exhibited in Dev-C++ (From: Richard Rehl <email@hidden>)
 >Re: Strange behavior in XCode, not exhibited in Dev-C++ (From: John Daniel <email@hidden>)
 >Re: Strange behavior in XCode, not exhibited in Dev-C++ (From: Richard Rehl <email@hidden>)
 >Re: Strange behavior in XCode, not exhibited in Dev-C++ (From: John Daniel <email@hidden>)

  • Prev by Date: Re: Strange behavior in XCode, not exhibited in Dev-C++
  • Next by Date: Re: Compile acts differently when run from terminal and in debugger???
  • Previous by thread: Re: Strange behavior in XCode, not exhibited in Dev-C++
  • Next by thread: Re: Strange behavior in XCode, not exhibited in Dev-C++
  • Index(es):
    • Date
    • Thread