• 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
[Q] Calling isEmpty on an NSRange?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Q] Calling isEmpty on an NSRange?


  • Subject: [Q] Calling isEmpty on an NSRange?
  • From: Ando Sonenblick <email@hidden>
  • Date: Mon, 23 Sep 2002 17:06:47 -0700

OK... So a range seems to be a mere struct and not a class instantiation.

Cool: I know I can get its length, location, etc via:

{
NSRange range;

range = [editor selectedRange];
return range.length;
}

But I've tried every which way to call isEmpty (and the other "actions")
with a range, but always get compile errors...

Can anyone elucidate?

Thanks,
Ando
_______________________________________________
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: [Q] Calling isEmpty on an NSRange?
      • From: Cameron Hayne <email@hidden>
    • Re: Just Shoot Me! - was [Q] Calling isEmpty on an NSRange?
      • From: Ando Sonenblick <email@hidden>
    • Re: [Q] Calling isEmpty on an NSRange?
      • From: Chris Hanson <email@hidden>
References: 
 >-methodForSelector: doesn't fail when it should (From: Andrew Duncan <email@hidden>)

  • Prev by Date: Re: Driving Word X from Cocoa.
  • Next by Date: Re: [Q] Calling isEmpty on an NSRange?
  • Previous by thread: -methodForSelector: doesn't fail when it should
  • Next by thread: Re: [Q] Calling isEmpty on an NSRange?
  • Index(es):
    • Date
    • Thread