[Info-vax] Text processing examples with Fortran requested

[Michael Moroney]

VAXman-  @SendSpamHere.ORG writes:

>In article <hdt0uo$eij$1 at pcls6.std.com>, moroney at world.std.spaamtrap.com (Michael Moroney) writes:
>>VAXman-  @SendSpamHere.ORG writes:

>>>In your opinion.  I've seen C coded projects scarier than waking up naked,
>>>after a night of bar-hopping, in a bed with Nancy Pelosi by your side and
>>>as unprofessionally executed as an Ed Wood film coupled with documentation
>>>as informative as graffiti tags along a railroad siding.
>>
>>That description is more like the _current_ code.  *Anything* would be
>>better.
>>
>>Well, almost anything.  There was one set of modules that were too
>>convoluted to get working under the Itanic macro compiler, that one of us
>>(not me) finally rewrote in C.  But it was rewritten almost line-by-line,
>>bug-compatible from Macro to C, because that's what the pointy-haired
>>manager wanted. It was the most hideous C code ever.

>OK.  I've never partaken in the rewriting Macro in C koolaid.  There's
>no way an algorithm coded in Macro won't compile and that *exact* same
>algorithm coded in C will.  Nope, I'm not putting that glass to my lips
>to swallow that tainted koolaid.

I am not a fan of conversion from Macro to C just for the sake of doing
so.  But some macro really, truly deserves it.

The macro mentioned does compile on a VAX but not Itanic.  There were
jumps all over the place, including between modules, as well as very ugly
stack manipulation, none of which were acceptable to the macro-32
compiler. The C rewrite did change the code enough to work around that,
but ugliness that didn't _have to_ change, didn't.

Even now, when someone mentions "QC modules" around here, a horse whinneys
in the background...

  unsigned int tmp;
  unsigned short *EntryAdd;
  EntryAdd=(unsigned short *) *((unsigned short *)tmp);