• 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: NSMakePoint and such - what about memory allocation?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSMakePoint and such - what about memory allocation?


  • Subject: Re: NSMakePoint and such - what about memory allocation?
  • From: Shaun Wexler <email@hidden>
  • Date: Thu, 20 May 2004 21:31:10 -0700

On May 20, 2004, at 8:22 PM, Wade Tregaskis wrote:

FWIW, this seems to stem from the fact that you don't get any sort of implicit constructor for structs, i.e. you can't embed NSPoint(x, y) in your code... this has annoyed me on hundreds of occasions; I can't even begin to imagine what the creators of C were thinking when they overlooked this.**

Yes you can. Just typecast it:

[object moveToPoint:(NSPoint){ x, y }];

;)
--
Shaun Wexler
MacFOH
http://www.macfoh.com
_______________________________________________
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: NSMakePoint and such - what about memory allocation?
      • From: Andreas Mayer <email@hidden>
References: 
 >NSMakePoint and such - what about memory allocation? (From: Christoffer Lerno <email@hidden>)

  • Prev by Date: Re: [firstPath appendBezierPath: [secondPath bezierPathByReversingPath]];
  • Next by Date: Re: Capabilities of Quartz: rotation? zooming?
  • Previous by thread: Re: NSMakePoint and such - what about memory allocation?
  • Next by thread: Re: NSMakePoint and such - what about memory allocation?
  • Index(es):
    • Date
    • Thread