You have still neglected to leave the user with the ability to use a different suffix. This suffix is already used by Alzabo::MethodMaker (for row columns) though it is configurable. If I intended to use both Alzabo and AutoCurry, I'd have to do some fancy footwork with the symbol table to rename all the curried functions before other _c functions were installed (or is it the other way, I forget).

Your accomodation may be as simple as providing an overridable package scalar.

BEGIN { $AutoCurry::Suffix = '_not_c'; }
use AutoCurry ':all';
[download]

Thanks for the friendly reminder.

I just uploaded version 0.1003 to CPAN. It includes the following addition:

=head2 Using another suffix

Do not change the suffix unless you truly must.

If for some reason you cannot use the standard C<_c> suffix, you
can override it by changing C<$AutoCurry::suffix> I<for the duration
of your calls to AutoCurry>.  Use C<do> and C<local> to limit the
scope of your changes:

    use AutoCurry;  # suffix changing is not compatible with ':all'

    my @curried_fns = do {
        local $AutoCurry::suffix = "_curry";
        AutoCurry::curry_package();
    };
    # result: ( "main::foo_curry" )

    sub foo { ... };
    # foo_curry will be created by call to curry_package, above
[download]

I cannot use the BEGIN approach that you suggested because that would override the suffix for all subsequent users of AutoCurry, not just the current package.

Tom Moertel : Blog / Talks / CPAN / LectroTest / PXSL / Coffee / Movie Rating Decoder

Ok, here's the BEGIN approach changed so it *does* work for you. I'm just creating a use() which has the value set for its duration. Any later calls to use() or ->import() won't reflect the suffix I set here.

BEGIN {
    local $AutoCurry::suffix = ...;
    require AutoCurry;
    AutoCurry->import();
}
[download]