Where should the type information be 215

in the early 70s, i wrote a pli program that analysed (360) buttembler listings ... creating abstract representation of instructions and doing detailed code flow analysis (as well as attempting to recognize register use before set scenarios ... aka are there code paths that failed to initialize a particular register needed later ... analogous to uninitialized variables).

it also attempted to represent the program in a pli-like psuedo syntax. branches translated into GOTOs ... but it also attempted to capture conditional branching ... and tranlate it into higher level conditional structions (aka while, if-then-else, do-until, etc).

on of the issues was that some of the branching logic ... which seemed moderately straight forward would translate into quite obtuse nested if-then-else structures 10 or more levels deep.

as referenced previously in the C-language thread ... while C-language programs tend to have a high proportion of buffer overflow failures (related to buffer constructs not carrying explicit length semantics), 360 buttembler code tended to have a high proportion of uninitialized (and-or incorrectly initialized) register failures ... aka register content management

most of these (register content) failures tended to be buttociated with anomolous and-or low frequency code paths. the issue with GOTOs, in attempting to do a "forensic" code path reconstruction, is reconstruction of the the actual code path followed. explicit conditional constructs tend to make specific code path instance reconstruction easier in specific failure scenarios.

--