non portable - a problem with direct access
in [Fortran]
|
Prev: McFor: a MATLAB-to-Fortran 95 Compiler
Next: 100% free dell laptaps offerd by dell and Vodafone companies.
From: Nick Maclaren on 3 Aug 2010 03:36 In article <4c5767c6$0$34573$c30e37c6(a)exi-reader.telstra.net>, robin <robin51(a)dodo.com.au> wrote: >| > >| >In the IBM S/360 and S/370 Fortran manual the sample programs >| >are printed as written on a "Fortran Coding Form." >| >| And a right damn-fool idea that was, too, especially for those of us >| who used paper-tape for input! >| >| TTYs came in in the mid-1960s > >TTYs were being used in 1960 and even earlier. >There were demonstrations used on remote installations >back in the 1950s. Sigh. Yes, of course I know that. It's not the point. They were specialist devices until the first time-sharing computers started to be used for real work, which was in the mid-1960s. And, even then, they were too scarce to be used for data entry, which was done offline, and they were used for editing, debugging, etc. This thread was about data entry. Regards, Nick Maclaren.
From: Nick Maclaren on 3 Aug 2010 03:44 In article <1jmlqtr.102d8o110yfgw0N%nospam(a)see.signature>, Richard Maine <nospam(a)see.signature> wrote: >Clive Page <junk(a)nospam.net> wrote: > >> >> > Screenshots? Are you serious? Why would the gfortran manual need >> >> > screenshots? That's ridiculous. >> >> I thought that I'd seen one somewhere, and I tracked it down: a very >> informative screenshot of the g95 compiler in action: >> >> http://sourceforge.net/project/screenshots.php?group_id=5179 > >I don't see anything at all informative about that screenshot that >wouldn't be just as well shown as text. In fact, all of the useful >content is text. The rest is nothing but an image of someone's (Looks >like Andy's) terminal emulator, which doesn't tell me anything about >g95. In addition to the problems you mentioned, that approach also makes it gratuitously hard for people with poor vision to read, and stops the use of the screen readers for blind people. For conveying information, plain text rules. For obfuscating it, then screenshots rule. Very useful in marketing! Regards, Nick Maclaren.
From: Clive Page on 3 Aug 2010 18:05 In message <1jmlqtr.102d8o110yfgw0N%nospam(a)see.signature>, Richard Maine <nospam(a)see.signature> writes >I don't see anything at all informative about that screenshot that >wouldn't be just as well shown as text. Sorry, my posting was intended to be ironic. Unfortunately I don't know the right smiley to use for irony, and anyway I should have remembered that Americans have problems with irony. :-) -- Clive Page
From: Richard Maine on 3 Aug 2010 19:03 Clive Page <junk(a)nospam.net> wrote: > In message <1jmlqtr.102d8o110yfgw0N%nospam(a)see.signature>, Richard Maine > <nospam(a)see.signature> writes > >I don't see anything at all informative about that screenshot that > >wouldn't be just as well shown as text. > > Sorry, my posting was intended to be ironic. Unfortunately I don't know > the right smiley to use for irony, and anyway I should have remembered > that Americans have problems with irony. :-) Ah. I did wonder at least a little bit, partly because although I can't say that I know you well, I did think I knew you enough to be surprised that you would think that screenshot useful. Guess I should have kept along that line of thought. :-( While on the subject, I might detect at least a bit of simillar humor in the web page itself. One (at least this one) more than half suspects that Andy saw that the site template had a spot for screenshots, so he put some it, fully knowing how silly it was. -- Richard Maine | Good judgment comes from experience; email: last name at domain . net | experience comes from bad judgment. domain: summertriangle | -- Mark Twain
From: robin on 3 Aug 2010 21:20
"Nick Maclaren" <nmm(a)gosset.csi.cam.ac.uk> wrote in message news:i38gtv$v58$1(a)gosset.csi.cam.ac.uk... | In article <4c5767c6$0$34573$c30e37c6(a)exi-reader.telstra.net>, | robin <robin51(a)dodo.com.au> wrote: | >| > | >| >In the IBM S/360 and S/370 Fortran manual the sample programs | >| >are printed as written on a "Fortran Coding Form." | >| | >| And a right damn-fool idea that was, too, especially for those of us | >| who used paper-tape for input! | >| | >| TTYs came in in the mid-1960s | > | >TTYs were being used in 1960 and even earlier. | >There were demonstrations used on remote installations | >back in the 1950s. | | Sigh. Yes, of course I know that. It's not the point. They were | specialist devices until the first time-sharing computers started | to be used for real work, which was in the mid-1960s. Liverpool University was using TTYs for time sharing in or prior to 1962. | And, even then, they were too scarce to be used for data entry, In the 1950s, and 1960s they were never "too scarce". They were manufactured by the thousands for telegraph work -- if not tens of thousands --and could be purchased from such manufactures as Creed, Siemens, and Teletype. | which was done offline, and they were used for editing, debugging, | etc. Sure, many of those in computer installations were used off-line because the only computer input mode was paper tape I/O. However, some systems had TTYs on line. |