[DGD] light-weight object creation, and virtual objects

[Noah Gibbs]

  If you make it with new_object rather than clone, it'll be a lightweight object.

  If you catch compile_object you can make a "virtual object" in the sense that you can alter the code before it gets compiled.  You could also create objects with filenames that aren't there (say, create all "mymap_XXX"-type objects in some algorithmic way for all XXX that are numbers), again by returning code from some other file (mymap.c, perhaps?) modified in some way by number.  There are many other ways to make "virtual rooms" for some meaning of that phrase, but that's one.

--- On Tue, 4/13/10, Tyler Littlefield <tyler at tysdomain.com> wrote:

> From: Tyler Littlefield <tyler at tysdomain.com>
> Subject: [DGD] light-weight object creation, and virtual objects
> To: dgd at dworkin.nl
> Date: Tuesday, April 13, 2010, 3:40 PM
> Hello all,
> I was working on a skill system, and was told to use a
> light-weight object setup in order to confine the overhead
> of each object. I started doing a bit of searching and found
> lots of 404s, before I came across the changelog and seen
> that the function new_object will create one. It says that
> if the master is a light-weight object, the descendant will
> be, as well. So, this brings up the question: IN the master
> object, what would mark  it as a light-weight object?
> 
> Last, I was told I could make a sort of "virtual object,"
> by catching compile_object, could someone explain this? I
> was trying to set up a way to create virtual rooms, and
> thought this might be of assistance.
> 
>         Thanks,
> Tyler Littlefield
>     http://tds-solutions.net
>     Twitter: sorressean
> 
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
>