[Info-vax] Text processing examples with Fortran requested

[VAXman- at SendSpamHere.ORG]

In article <hdt0uo$eij$1 at pcls6.std.com>, moroney at world.std.spaamtrap.com (Michael Moroney) writes:
>VAXman-  @SendSpamHere.ORG writes:
>
>>In article <hdsrvc$9ag$1 at pcls6.std.com>, moroney at world.std.spaamtrap.com (Michael Moroney) writes:
>>>VAXman-  @SendSpamHere.ORG writes:
>
>>>>>(oh how I wish we could simply start over in another language. Pointy-
>>>>>haired managers dictate otherwise)
>>>
>>>>What?  Like C?  Try writing a parser to find all the zany things people
>>>>do with that hieroglyphic and you'll be pining for that Macro you have 
>>>>now.
>>>
>>>If _we're_ writing the C (or whatever), our code will be _much_ cleaner
>>>overall.  I may be crazy, but not _that_ crazy.
>
>>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.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

  http://www.quirkfactory.com/popart/asskey/eqn2.png
  
  "Well my son, life is like a beanstalk, isn't it?"