• 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: Flame retardant
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Flame retardant


  • Subject: Re: Flame retardant
  • From: Chris Purcell <email@hidden>
  • Date: Thu, 23 May 2002 13:31:56 +0100

"Odd, I don't recall that being a particularly frequent question. In any
case, it sounds as if you don't want people asking questions that are in the
documentation, but don't want them asking where to find the documentation,
either. What, then, are they to do?"

C'mon, if you do not know that the documentation is in the same directory as
Project Builder you need more assistance than this list can support.

You do appreciate, of course, that:
a) Installing the documentation is entirely optional
b) Installing the documentation takes several hundred megabytes of space
c) On my original iBook, I have almost nothing installed besides OS X and Apple's coding tools, and I am still close to having no room left. If I wanted to install, say, Office X, the documentation would have to go
So people may not *have* the docs installed, and may not know they are duplicated on the Apple site.

" Hence, there is no clear line between Objective-C and Cocoa, and questions
about Objective-C are entirely appropriate for this list."

That is entirely wrong, you can write a complete program in Objective C that
uses none of the Cocoa frameworks. You can write a command line Objective C
program for instance.

Cocoa encompasses Foundation, not just AppKit. You cannot use ObjC without a base class, and NSObject is part of Cocoa. You *can* write a command line tool that doesn't use Foundation, but then you are just compiling ANSI C code with an ObjC compiler!

"I don't see the problem here. Objective-C is a superset of C, so you can't
write Objective-C without also writing plain C, too....."

I disagree because if you do not know ANSI C, basic control constructs and
simple data structures you have no business jumping into Cocoa. I went
through the pains of learning how to program before I got to this level and
everyone else has to.

"Jumping into Cocoa"? People sometimes learn a language because they need to use it, you know! Just because you were able to learn C before ObjC doesn't mean everyone else can. I learned C++ before ANSI C, for instance.

Also, advice to those giving advice, don't always just give an
answer,....teach the new programmer to search a bit by holding their hand so
to speak and make them better programmer who learn to use their instinct to
find the answers they need.

That, I agree with wholeheartedly. But I think most people do that anyway.

Kritter out
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Flame retardant
      • From: Ondra Cada <email@hidden>
  • Prev by Date: Re: Cycle Through Windows
  • Next by Date: Re: Dynamic Languages [was: Re: why Obj-C]
  • Previous by thread: Re: Flame retardant
  • Next by thread: Re: Flame retardant
  • Index(es):
    • Date
    • Thread