Signature with import functions

[DavidRaab]

Example Sq::Parser

The current approach with importing doesn't work. When i write.

use Sq;
use Sq::Parser;
use Sq::Sig::Parser;

then this does not work as expected. Sq::Sig::Parser adds type-checks to the function in Sq::Parser but the type-checking is added after the functions was imported in the current package. So the function in the current package don't have any Signatures.

[DavidRaab]

Maybe i write the Exporter in a way that you can specify.

use Sq::Parser sig => 1

and then it loads the signature before exporting.

[DavidRaab]

I have something like this in mind.

use Sq;
use Sq::Parser -sig => 1;

this will load the default signature that was defined in Sq::Parser itself. You also can do.

use Sq;
use Sq::Parser -sig => 'Sig::SomeDifferent';

this then loads another signature by default.

[DavidRaab]

I also consider those option:

use SomeModule 
    -as => 'WhereverYouWant',
    -var => $var,
    -prefix => 'tp';

i don't know if var is possible without rethinking modules completely.

[DavidRaab]

-var => $var is possible.

When this parameter is passed i just could return a Hash. This Hash than contains all functions of the symbol-table in that
package, and put's it in the hash. Then it is returned.

The problem with that is, not every function makes sense to be exported this way, becaus some may be methods on object. But the user could supply a list that is ok to be exported this way. So someone could still call all constructors or
static functions on it.

For example it could be.

use Sq::Type -var => $t;

then a user could do:

$t->{t_or}->();

but this is less practical. But i could return a blessed Hash with AUTOLOAD that automatically dispatches a method call on it to a hash-key. Also the names then could be different. For example the t_ could be removed. So someone then could finally write.

$t->or();

but. What's the difference to just import the functions with a namespace?

t_or();

It's basically the same. Still shorter. And is definetely a lot faster! All this blessed Hash exporting and AUTOLOAD will make it slower. With basically no advantage. It would just replace an underscore with -> and you need to add $. So actually this seems completely pointless.

[DavidRaab]

It would just replace an underscore with -> and you need to add $. So actually this seems completely pointless.

But i guess people go crazy about it, because then it is object-oriented and you call those shiny methods. The other is just procedural crap, right?

[DavidRaab]

Procedural? It just looks on the surface. It's full of Combinators!

[DavidRaab]

Maybe i write the Exporter in a way that you can specify.

use Sq::Parser sig => 1

and then it loads the signature before exporting.

At least this part is now implemented in Sq::Exporter