Which do you think is better and why? (Use of alias)

[Phoenixia]

If you were going to write a script that modified several rgss methods, what would be better overall: to use alias and ,then, just add the new defs in the script, or instruct the user to overwrite the originals in the editor? The second case would seem to make for a slightly tighter set of code and would not require checking to see what is aliased later (you shouldn't have to jump around through code to see how a method is defined) On the other hand, if you needed to remove the script, or just wanted to test it, it would seem like the alias method would make this easy by centralizing everything; moreover, if the user chose to keep it, they could overwrite the originals if they so chose. What are your thoughts? Any substantive reasons to prefer one over the other?

 

[Atoa]

Something i always tell people: NEVER EVER tells people to rewrite the original scripts, unless it's for personal use.

If you making scripts to submit into forums or something like that, you must consider that there's people that are totally newbie in terms of scripts, and the more plug-and-play the script is, the better.

Even if you need to rewrite an whole method, it would be better make an new section with the rewrited method.

 

[gerrtunk]

I agree, the gains of not using alias are very low, just a small speed improvement, i think, and the f12 bug?, the rest, is better with it.

If you are modifying a very high rendiment script, maybe... but.

Even if you need to rewrite an whole method, it would be better make an new section with the rewrited method.

Why?

 

[Phoenixia]

I tend to agree, I figure if people wanted to overwrite it they could. However, it seems bad that it obscures where the method def is; which incidentally was the problem with using goto. Im torn as it seems good for rgss, but bad in general. But I agree strongly with the plug and play aspect.

 

[Atoa]

The F12 bug is caused by improperly coded scripts in most case.
Using alias on methods that only exist on the parent class instead of using a super.

 

[ForeverZer0]

Always use an alias when submitting code for others to use. When they decide to release there game, they can very easily "hard-code" it all themselves.

 

[BlueScope]

Yep, aliasing is definately the way to go for released scripts - not only because it makes scripts plug-and-play, but also because it clearly illustrates to people what needs to be changed and where. That way, even when two scripts change the same method and someone wants to 'hard-code' it (I'll just take over that term now :p ), they know what to do with it without much looking through, trying to figure out where to copy code from and why, always wondering if they missed something.