Re^2: compiletime checking of valid method calls

> What if the code adds new subroutines at runtime?

My objective is to be better than the export constant solutions.

And I'm only seeing this "solution" activated in the test/dev phase.*

So if a method is added at runtime it would need to be "pre-registered" at compile time, much like a constant would need to be declared at compile time.ł

We don't add methods at compile time, and our "use" of OO is probably best described as weird QQ.˛

DISCLAIMER: I can't choose my colleagues and bosses and I don't have any alternative workplaces at disposal yet.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

*) in other words it's not weirder than using PPI for this in a .t test.

˛) My colleagues don't know how to add methods at compile time yet.

ł) or checking would be deactivated by omitting the type information.

Comment on Re^2: compiletime checking of valid method calls