My problem in hindsight is that it's hugely time consuming compared to any WYSIWYG report designer.
I WROTE a report "designer" in Fortran back in the late 70s. That was huge fun -- lots of math... C Hal Kaplan wrote: > Chet Gardner wrote ... > > => Those of us who had to work on IBM mainframes, just as those > => of us subjected to windoze now, had to suffer through that period. > => > => Anyway, I prefer VFP... I/O WAS a bear in Fortran... > => > > I have two general comments to make and they are not directed at Chet > specifically. > > First, I am no fan of IBM for several reasons but there was a certain > "system" aura associated with their products that, to me, echoed the very > nature of my view of computers: Precise. Unwavering. Totally predictable. > Dumb, really dumb. > > Second, what is the problem with FORTRAN I/O that (almost) everyone is > complaining about? READ (unit,format)field_list Is that any worse than > low-level I/O in VFP? Oh sure, Format descriptors could be problematic but > only because they are so flexible and powerful. You don't get something for > nothing and FORTRAN delivered a very big "something," although it will never > replace Assembler or <sigh> machine code. > > B+ > HALinNY > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
