trizen / trizen/sidef

override built-in classes

Open
#38 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
126
Forks
2
Avg merge
15m
Merged PRs (30d)
3

Description

Would be good if you could do:

my $interpreter = Sidef->new(
   classes => {
      Sys   => 'My::Sidef::Sys::Sys',
   },
);

And that instance of Sidef would use My::Sidef::Sys::Sys instead of Sidef::Sys::Sys. This would allow you to run scripts in a safe evaluation context which didn't have access to Sys.exec() and so on.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Sidef->new configuration path and trace how built-in classes such as Sidef::Sys::Sys are selected for an interpreter instance. Done means an instance can substitute the requested class, allowing a safe evaluation context without access to operations such as Sys.exec().

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.