• 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: RFC: Allocating via a protocol/interface
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: Allocating via a protocol/interface


  • Subject: Re: RFC: Allocating via a protocol/interface
  • From: Edwin Zacharias <email@hidden>
  • Date: Mon, 1 Jul 2002 22:07:04 -0400

The goal is to be able to allocate a class that isn't known at compile time, based on the output of a function.

A class is actually a struct. You could malloc one and use objc_addClass() to add it to the runtime. There may be an easier way to do this.

You want to be able to load new classes that weren't known when the program was written.

Restricting the loading to just one class isn't going to add security. That class can still do anything to any class it wants to. Also, I doubt this would be possible. I don't think you can know what's in a binary without loading it. Could you explain more about why you want to do this?

- Edwin
_______________________________________________
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: RFC: Allocating via a protocol/interface
      • From: Michael Gersten <email@hidden>
  • Prev by Date: Re: Can't cram an NSRange into an NSArray?
  • Next by Date: Strange Question
  • Previous by thread: Re: Can't cram an NSRange into an NSArray?
  • Next by thread: Re: RFC: Allocating via a protocol/interface
  • Index(es):
    • Date
    • Thread