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

Signature of withPerl5 gives little clue as to its use. #12

Open
phlummox opened this issue Feb 4, 2021 · 0 comments
Open

Signature of withPerl5 gives little clue as to its use. #12

phlummox opened this issue Feb 4, 2021 · 0 comments

Comments

@phlummox
Copy link
Owner

phlummox commented Feb 4, 2021

The withPerl5 function has a rather opaque signature that gives no clue that it's effectively "bracket"-ing an implicit, global Interpreter.

The function's usage could be made more obvious if Interpreter objects were explicitly allocated and finalized (rather than a single global instance being operated on). Then, withPerl5 would take a function which took an Interpreter object, its signature would give a better idea of its purpose, and it'd be more flexible, too.

This shouldn't be hard to do - the perlembed docco gives examples of how to work with multiple interpreter instances.

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

1 participant