yeah, I am really not worried about the performance on this one, just noted
it for completeness.
What is nagging at me is what kentnl mentioned where something nested
catches an exception from something that failed to release it's context due
to the exception. Not because of these vars, but
One remaining question.
Should the context maintain a stack, where each time context() is called
(nested) it pushes the vars to the stack, and each call to release pops it,
or should it just store them on creation, do nothing on retrieval, and only
restore them on the final release?
Right now
[Top-posted]
The extra cost would be:
1. Array storage
2. Push
3. Pop
At the cost of supporting any level of nesting, I think it's a negligible
cost, but I would profile it.
On Wed, Jan 13, 2016 at 7:50 PM, Kent Fredric wrote:
> On 14 January 2016 at 07:39, Chad Granum
On 14 January 2016 at 07:39, Chad Granum wrote:
> Right now the version I have up on cpan just stores them on creation, and
> restores them on final release. Nothing happens for nested calls to
> context()/release(), all my downstream testing shows no breakages (not a
> full
4 matches
Mail list logo