Re^2: static method checker for perl?

Even prototyped functions take a list. They just define what's in the list.

While that may be technically true (Perl uses a stack), I'm not sure that's helpful. Prototyped functions parse differently from regular Perl functions, so the apparent behavior of these functions may not make it apparent that they take lists of arguments.

Comment on Re^2: static method checker for perl?

Replies are listed 'Best First'.
Re^3: static method checker for perl? by DStaal (Chaplain) on Apr 08, 2009 at 18:22 UTC
Agreed. I just wanted to indicate I was aware of prototypes. (I didn't feel a more in-depth discussion on them was needed to answer the question given.) But yeah, prototypes cause the function to apply different contexts to their arguments (except when they don't) and so they can appear to take something other than a list. Unless you ignore the prototype. Or work around it some way. Or... End result, for this discussion: Prototypes in Perl don't actually help all that much with static code analysis. They can help a bit, but not enough to make code analysis really useful.	[reply]

Replies are listed 'Best First'.

Re^3: static method checker for perl?
by DStaal (Chaplain) on Apr 08, 2009 at 18:22 UTC

Agreed. I just wanted to indicate I was aware of prototypes. (I didn't feel a more in-depth discussion on them was needed to answer the question given.)

But yeah, prototypes cause the function to apply different contexts to their arguments (except when they don't) and so they can appear to take something other than a list. Unless you ignore the prototype. Or work around it some way. Or...

End result, for this discussion: Prototypes in Perl don't actually help all that much with static code analysis. They can help a bit, but not enough to make code analysis really useful.

[reply]