UI: Qs to get the ball rolling
Sun, 12 Mar 95 10:21 EST
> When you've a large system, with pieces supplied by several vendors,
> and part of it isn't working, how do you isolate the problem?
If parts can eventually be proven correct, vendors of buggy
parts will be the shame of computer industry. Then, "bugs" will
exist only as one thing: people writing programs without
understanding what these program should actually do.
Um... let me rephrase that: if several components working together do
not achieve their desired result, how do you decide which are faulty?
Remember that you have to solve this problem before the components are
written if the components are to be written correctly.
Thanks to active annotations, the system will also be its own
interactive debugger if needed.
This has some promise...
#!/usr/local/bin/perl -- export-a-crypto-system sig, RSA in 5 lines of PERL:
"$0 -d|-e key mod <in >out\n"if$s!~/^-[de]$/||$#ARGV<2;$v=$w;$s=~/d/?$v-=2:
`echo 16o16i\U$m\Esm\U$n\Esn$c|dc`);print pack('H*','0'x($v-length$a).$a);}