Item13287: /o is poison

Priority: Urgent
Current State: Closed
Released In: n/a
Target Release: n/a
Applies To: Engine
Branches: master
Reported By: CrawfordCurrie
Waiting For:
Last Change By: CrawfordCurrie
After a discussion with George about /o and some background reading and thinking, I have concluded that /o is poisonous, and at high risk of creating bugs.

The main scenario I foresee is where /o has been used on a RE that interpolates a cfg var. cfg vars are supposed to be constant, but there are cases where we need to change them dynamically. Since /o applies the first time the RE is evaluated, it may be a lottery as to a before-change or after-change value is picked up for the interpolated var.

The safest course is to remove all /o's from core code.

-- CrawfordCurrie - 01 Mar 2015

Topic revision: r2 - 01 Mar 2015, CrawfordCurrie
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy