I hate bashing Xcode since I use it on a daily basis but there are other weird things happening such as Xcode throwing errors when compiling a command-line app that builds and executes fine using gcc, g++, and/or clang and a Makefile. When I see anomalies like this, I wonder how reliable Xcode is. If a program builds and executes on multiple linux, PPC, and Intel platforms with gcc, g++, and clang (as appropriate for the platform) yet can't compile when sucked into Xcode, how do I debug this? Funny thing is I used to use Xcode as my primary source code "fixer" but at the moment, clang is the best source code "fixer" - and it's running on an ARM-based Raspberry Pi2 under bleeding-edge Ubuntu 15.04. Now my last step is bringing the source into Xcode and inevitably finding it throwing some strange error message (the errors vary from build to build). One recurring error is Xcode failing to find externally declared functions in an included header file. This is probably a clang problem though as I also recall having to switch some plain old C files to use gcc or g++ rather than clang to get around the problem when running with the Makefile. Can't do that in Xcode, it only knows clang so those functions which clearly exist and run correctly when using gcc/g++ fail inside Xcode. Debugging-wise, my favorite feature in CW was being able to expand data structures and for that matter, any part of memory to display as hex, octal, binary, decimal, or even character strings. That was a great feature, sometimes it's easier to debug pointer problems when you can look at the data in different formats. What makes no sense in hex pops to life when displayed as a string - and vice versa. And ditto on the window thing - I never know when I click on a source file if it'll open in the main window or in a new window. Sometimes I end up with the same file displayed in both the main window and a separate window. Sounds like we need to call ghost busters.... On Wednesday, June 24, 2015 4:15 AM, Dave <[email protected]> wrote: On 23 Jun 2015, at 02:21, Tony Scaminaci <[email protected]> wrote: Apple listened to Taylor Swift, I hope they take note of what we're complaining about. I doubt it! The only reason I post here is in the hope that someone will know of a 3rd party tool that in some way restores the features I like. They would do well to fire up an old copy of CW and look at how easy debugging was in that tool. It’s not just debugging, searching for instance was *much* better/easier in CW, with options to do get the results however you wanted them, either a list similar (but better) then the way XCode does it now, or you could search for something and, when you hit Command+G it would open the next file that contained what you were searching for (Option+Command+G would close the current window behind you - how cool is that?!?). Windows remembered their position too, now XCode suffers form advance early onset dementia when it comes to where to put the window - especially if you have > 1 monitor (I have 4!). How hard can that be? XCode 3 did it, why take this out of XCode 4+? XCode at the moment reminds me of the awful interface that the Apple Movie Player suddenly got - everyone and their brother knew it was horrid but it was stubbornly left as it was for its lifetime for no other reason that I can make out than to prove that “Apple can never be wrong”. CheersDave _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/friskythecat%40sbcglobal.net This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
