M
Michael Griffin
On June 19, 2003 23:53, Lynn at Alist wrote: <clip>
> Unfortunately, they didn't look through the code itself. The contractor
> had run some form of filter thru 95% of it. Literally all comments were
> striped, all variables and function calls had been renamed to things
> like int2345 and func0345(). And the 5% that missed the filter had all
> comments and variable name in a foreign language.
> So in effect they had nothing really usable - even though they had the
> source code. ;^]
<clip>
This sounds like something that used to be called "shrouded source code". I haven't heard of it in a while, but it was used at one time for distributing libraries. You could compile it so it was to some degree portable, but it was impractical (or at least extremently difficult) to see how it actually worked.
Of course, quite a few people produce Visual Basic programs that look like that without needing any additional help at all...
--
************************
Michael Griffin
London, Ont. Canada
************************
> Unfortunately, they didn't look through the code itself. The contractor
> had run some form of filter thru 95% of it. Literally all comments were
> striped, all variables and function calls had been renamed to things
> like int2345 and func0345(). And the 5% that missed the filter had all
> comments and variable name in a foreign language.
> So in effect they had nothing really usable - even though they had the
> source code. ;^]
<clip>
This sounds like something that used to be called "shrouded source code". I haven't heard of it in a while, but it was used at one time for distributing libraries. You could compile it so it was to some degree portable, but it was impractical (or at least extremently difficult) to see how it actually worked.
Of course, quite a few people produce Visual Basic programs that look like that without needing any additional help at all...
--
************************
Michael Griffin
London, Ont. Canada
************************