in reply to Re^3: Troubles creating a .exe
in thread Troubles creating a .exe

One should have thought PerlApp could try to find itself the modules it uses.

Well, it tries as best it can ; there is no substitute for testing/manual intervention :)

:) IIRC the phrase goes one should think ... :)

Replies are listed 'Best First'.
Re^5: Troubles creating a .exe
by CountZero (Bishop) on Feb 27, 2012 at 10:00 UTC
    Well, obviously PerlApp is not doing a good job then.

    CountZero

    A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

    My blog: Imperial Deltronics

      Well, obviously PerlApp is not doing a good job then.

      Well obviously you're expecting magic

        I am expecting no magic at all.

        PAR does a better job and there is no magic involved, just a thorough dependency scanning.

        I grant you that there will always be edge-cases where dependency scanning will miss something, but I never had to add all of the used modules (and the modules used by these -- recursively) by hand.

        CountZero

        A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

        My blog: Imperial Deltronics