Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
[RGSS] SELF.DESTROY
Posts
Pages:
1
Zachary_Braun
View playlists
CloseHello all,
Is there a way for objects to destroy themselves using the self-referential "self"? Code that achieves the effect of "self = nil"?
Is there a way for objects to destroy themselves using the self-referential "self"? Code that achieves the effect of "self = nil"?
Is there a way to code that into homemade classes? Let me type an example:
Actually, I just realized that you don't need the "self", just write "dispose"... Why does "self" exist if you can just reference the method that's already there?
class My_Class
def initialize(timer, sprite_name)
@timer = timer
@sprite = Sprite.new
@sprite.bitmap = RPG::Cache.pictures(sprite_name)
end
def update
@timer -= 1
if @timer < 1
self.dispose
end
end
def dispose
@sprite.dispose
# ??? Could anything else go here to completely
# get rid of this My_Class object from memory?
end
end
Actually, I just realized that you don't need the "self", just write "dispose"... Why does "self" exist if you can just reference the method that's already there?
Yeah, your example is pretty much there. Just do @sprite = nil after the call to dispose and you're golden.
For the most part, you're right: self is mostly redundant. It can help to disambiguate between class methods, instance methods and local variables, though.
Let's say you have a class with an instance variable "some_var", and the class also has a method which takes a parameter, also called "some_var". If you need to do something to both of them in the same method, you're going to run into an issue:
some_var = whatever
some_var = whatever else
This is going to perform both operations on the local variable. However...
self.some_var = whatever
some_var = whatever else
This will assign whatever to the instance variable and whatever else to the local variable.
You'll find in a lot of cases in the VX Ace default scripts, the references to self are mainly just there to clarify that methods can be called by a class without having an instance, or to avoid confusion when the variable is named something you might mistake for a local variable in the context of the method.
For the most part, you're right: self is mostly redundant. It can help to disambiguate between class methods, instance methods and local variables, though.
Let's say you have a class with an instance variable "some_var", and the class also has a method which takes a parameter, also called "some_var". If you need to do something to both of them in the same method, you're going to run into an issue:
some_var = whatever
some_var = whatever else
This is going to perform both operations on the local variable. However...
self.some_var = whatever
some_var = whatever else
This will assign whatever to the instance variable and whatever else to the local variable.
You'll find in a lot of cases in the VX Ace default scripts, the references to self are mainly just there to clarify that methods can be called by a class without having an instance, or to avoid confusion when the variable is named something you might mistake for a local variable in the context of the method.
Pages:
1
