Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perhaps use Module::Compile instead of Filter::Simple #1

Open
jwrightecs opened this issue May 8, 2023 · 2 comments
Open

Perhaps use Module::Compile instead of Filter::Simple #1

jwrightecs opened this issue May 8, 2023 · 2 comments

Comments

@jwrightecs
Copy link

BENEFITS

Module::Compile compilers gives you the following benefits:

  • Ability to mix many source filterish modules in a much more sane manner. Module::Compile controls the compilation process, calling each compiler at the right time with the right data.
  • Ability to ship precompiled modules without shipping Module::Compile and the compiler modules themselves.
  • Easier debugging of compiled/filtered code. The .pmc has the real code you want to see.
  • Zero additional runtime penalty after compilation, because perl has already been doing the .pmc check on every module load since 1999!
@ingydotnet
Copy link
Collaborator

You forgot to mention that I(ngy) wrote Module::Compile!!!

I started with Module::Compile but then realized it's really only made for modules, not Perl .pl files.
So I switched to Filter::Simple for now.

It's likely that I'll switch to Module::Compile later, once I get the thing a little further along.

Maybe let the user select with something like use assign::0 -compile;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@ingydotnet @jwrightecs and others