in reply to Re: How to avoid $_ in grep
in thread How to avoid $_ in grep
I'd agree with the above; also, maybe it is possible to put a thicker line between things that 'custom users' need or are allowed to change ?
Maybe offering a distinct Config file, or separating the allowed/easy to change code in front of the scripts or even distinct modules ?
If the users are really meant to tamper the very hearth of underlying algorithms and so, $_ would probably be the smallest difficulty to overcome.
Maybe you can do yet another thing, as I'm just learning from the book I mention in the signature below:
can you offer them some placeholder subs and use callbacks, so that they could easily manage their own particular code snippets within the otherwise bigger code machinery ?
Maybe offering a distinct Config file, or separating the allowed/easy to change code in front of the scripts or even distinct modules ?
If the users are really meant to tamper the very hearth of underlying algorithms and so, $_ would probably be the smallest difficulty to overcome.
Maybe you can do yet another thing, as I'm just learning from the book I mention in the signature below:
can you offer them some placeholder subs and use callbacks, so that they could easily manage their own particular code snippets within the otherwise bigger code machinery ?
|
|---|
In Section
Seekers of Perl Wisdom