When the following code is ported into a language which detects and the rejects the propagation of undefined values form variable to variable.. I see this is happening in our java script code.
Looking at the code below as it flows into the for loop and into the complex branch of if statements
I see e1 can be read before it is set. ( I have edited the line with a comment )
and when I run one of the standard tests -- using a debugger.
I see the subsequent line
if (e0 && e1 ) {}
being computed as
if (undefined && 8 ) {}
this works ok because the natural initial value for e1 is actually 0b0000
Anyway this "read before write error" should be removed as it is a maintenance hazard.
This is a minor cosmetic change.
When the following code is ported into a language which detects and the rejects the propagation of undefined values form variable to variable.. I see this is happening in our java script code.
Looking at the code below as it flows into the for loop and into the complex branch of if statements I see e1 can be read before it is set. ( I have edited the line with a comment )
and when I run one of the standard tests -- using a debugger. I see the subsequent line
if (e0 && e1 ) {}
being computed as
if (undefined && 8 ) {}
this works ok because the natural initial value for e1 is actually 0b0000
Anyway this "read before write error" should be removed as it is a maintenance hazard.