• 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: xcode-users digest, Vol 1 #611 - 11 msgs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xcode-users digest, Vol 1 #611 - 11 msgs


  • Subject: Re: xcode-users digest, Vol 1 #611 - 11 msgs
  • From: Shawn Erickson <email@hidden>
  • Date: Thu, 26 Aug 2004 14:24:38 -0700

File a bug if you have not yet done so... <http://developer.apple.com/bugreporter/>

-Shawn

On Aug 26, 2004, at 1:40 PM, Massimo Marino wrote:

Indeed, but how are you going to justify changing system files? The issues arises, e.g., with /usr/include/time.h and /usr/include/signal.h . I certainly cannot offer as a solution the change of code in /usr/include.

Xcode *should* not have an issue with distinguishing <.> and " " in #include.

The funny thing is that after having chosen SealBase/Time.h deep into folder structure then it complains it cannot find other .h files in SealBase included by Time.h because SealBase (!) is not in the Header Search Path.

Cheers

PS
It is more likely asking the mechanic to fix the car because it sputter when I switch on the radio and then not allowing the mechanic to dismount the engine to find the fix. Hardly a problem with the engine.


On Aug 26, 2004, at 4:36 PM, email@hidden wrote:

Message: 9
From: Keith Ray <email@hidden>
Subject: Re: time.h vs Time.h
Date: Thu, 26 Aug 2004 07:04:41 -0700
To: Xcode Users <email@hidden>

Both of your statements are like going to a mechanic, asking him to fix
your car, but telling him he's not allowed to open the hood or replace
any parts.


You may be able to use CodeWarrior - it can distinguish between <> and
"" includes if you set it up right.

On Aug 25, 2004, at 8:57 AM, Massimo Marino wrote:

I do not think you may install Xcode on UFS. If instead the suggestion
is to have a partition were to put source code would not work. Could
not tell OS X users to repartition their HD if they want to use Xcode.
It is supposed to work with C++ without the "caveat: watch how you
name your classes".


Renaming the code is also not a solution: it runs on Linux and
Windows. Asking to change MLOC to have it run on OS X and Xcode would
be just calling for killing OS X itself.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.


References: 
 >Re: xcode-users digest, Vol 1 #611 - 11 msgs (From: Massimo Marino <email@hidden>)

  • Prev by Date: Scrolling in Xcode 1.5 editor
  • Next by Date: Plugin is 10X too big!
  • Previous by thread: Re: xcode-users digest, Vol 1 #611 - 11 msgs
  • Next by thread: Scrolling in Xcode 1.5 editor
  • Index(es):
    • Date
    • Thread