Re: [Rails-spinoffs] why some features uses new and some just static function call

[Ryan Gahl]

Hmm, I'm pretty sure they can all be used either way, since functions are first class objects (you can either invoke or instanstiate, and instantiation also causes invocation of the constructor, which in this case is also the meat and potatoes)...

I think instantiation of the Effects, et. al., depends on whether or not you need a handle to it for some other purpose later, or maybe for settings/memory re-use.

On 6/13/06, Reynard Hilman <[EMAIL PROTECTED]> wrote:

Hi,

when using prototype and scriptaculous, isn't it confusing sometimes to remember which ones you have to use new and which ones that are just static function call.

For example:
new Insertion.Before (...);
new Effect.Opacity(...)

Effect.Fade(..);
Effect.Appear(...);

I havent really looked at the implementation, but out of curiosity, I'm just wondering is there a reason some of the function must instantiate new object, most of the time you dont even use the object after instantiating it. am I correct?

thanks,

- reynard

_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs