1710 Pack Press Any Key to Continue

Press any key to continue?

 Press any key to continue?

Author	Message
	Press any key to continue? Quote: >I'd just want to add: when I was new using computers, I never had >trouble pressing any key - I thought is was pretty straightforward >English, and I am not a native English speaker! >However I did have trouble finding the RETURN key. I had an ENTER key, >but it took me several weeks to figure out that they were the same. I am not a native english speaker either, so maybe I misunderstood, but Return and Enter key are not the same. Although the difference today is less known that it was, apart from the return key being the left one on an average keyboard, and enter key being the right-down one, there is also the difference in their function. For which I leave you with wikipedia, or EDT editor which one used to use under msdos :-) Quote: >At least telling a user to press "any" key had double meaning; one may >interpret it the right or wrong way. However there is nothing in >standard English to suggest that the words Return and Enter are >somehow synonymous. One has to have good background in computer >history for this to be naturally understood. pozdrav dig
Sat, 18 Sep 2010 01:56:33 GMT
Dave Seama #17 / 30	Press any key to continue? Quote: > However I did have trouble finding the RETURN key. I had an ENTER key, > but it took me several weeks to figure out that they were the same. My keyboard has both a RETURN key and an ENTER key.  Although they can be used interchangeably most of the time, they send different keycodes and there are a few applications that actually distinguish between the two. Mathematica is one example.  A RETURN simply means I want to continue typing on the next line, while an ENTER means to evaluate the expression in the current cell. -- Dave Seaman Court affirms Judge Yohn's ruling. <http://www.ipsnews.net/news.asp?idnews=41761>
Sat, 18 Sep 2010 03:24:48 GMT
GaryScot #18 / 30	Press any key to continue? Quote: > > > Why not just "Press RETURN to continue" ? <snip> > However I did have trouble finding the RETURN key. I had an ENTER key, > but it took me several weeks to figure out that they were the same. I used to use a terminal that had a key called RETURN that was separate from ENTER.  RETURN issued a CR character, ENTER issued a different code (don't remember which tho).  Software treated them the same or different depending on context. Quote: > At least telling a user to press "any" key had double meaning; one may > interpret it the right or wrong way. However there is nothing in > standard English to suggest that the words Return and Enter are > somehow synonymous. One has to have good background in computer > history for this to be naturally understood.
Sat, 18 Sep 2010 06:21:19 GMT
Bamm #19 / 30	Press any key to continue? There's been so much discussion on my original post, but in the end, the answer is simply, it can't be done in fortran. Thanks for all the suggestions though.
Sat, 18 Sep 2010 10:42:23 GMT
Richard Mai #20 / 30	Press any key to continue? Quote: > There's been so much discussion on my original post, but in the end, > the answer is simply, it can't be done in Fortran. Thanks for all the > suggestions though. Basically, that's right. There can sometimes be system-dependent ways that might be acessible from Fortran, but it can't be done directly "in Fortran". Which makes it even more puzzling why such a translation would be assigned as part of a homework. Translating something from Basic to Fortran (particularly an old version of Fortran) seems like an odd homework problem in the first place. It wouldn't fit well in a typival Fortran class (because of the assumption that you know Basic). It would fit even less well in a typical Basic class. It seems even more odd when it is something that can't properly be translated. I suppose it could possibly be intended as an illustration of language diferences, but it would be a rather "{*filter*}" approach to assign an "impossible" homework problem and let you figure out that it is impossible. I've seen profs do things like that, but it isn't common. It leads one to suspect more mundane explanations. -- Richard Maine                    | Good judgement comes from experience; email: last name at domain . net | experience comes from bad judgement. domain: summertriangle           |  -- Mark Twain
Sat, 18 Sep 2010 12:11:56 GMT
Gerry For #21 / 30	Press any key to continue? Quote: > There's been so much discussion on my original post, but in the end, > the answer is simply, it can't be done in Fortran. Thanks for all the > suggestions though. It can be done in fortran, if only by binding C: #include <stdio.h> int main(void) { int ch = '*'; ++ ch; putchar(ch); putchar('\n'); printf ("Press carriage return\n"); getchar(); Quote: } // gcc -o plus plus.c This program displays a plus and hangs around because of the getchar call. I believe that the printf is the only thing that can't be bound here. system ("pause"); is another one to remember.  Pause is something windows understands, if that's your game. -- "I am waiting for them to prove that God is really American." ~~  Lawrence Ferlinghetti
Sat, 18 Sep 2010 13:24:37 GMT
user #22 / 30	Press any key to continue? Quote: >> There's been so much discussion on my original post, but in the end, >> the answer is simply, it can't be done in Fortran. Thanks for all the >> suggestions though. > It can be done in fortran, if only by binding C: > #include <stdio.h> > int main(void) > { > int ch = '*'; > ++ ch; > putchar(ch); > putchar('\n'); > printf ("Press carriage return\n"); > getchar(); > } > // gcc -o plus plus.c > This program displays a plus and hangs around because of the getchar call. > I believe that the printf is the only thing that can't be bound here. > system ("pause"); > is another one to remember.  Pause is something windows understands, if > that's your game. You missed the point, as did I at first. He wants the user to be able to press "any" key, not just the "return" key. Btw, if "return" key is good enough, you could use the fget intrinsic supplied by g77, no need for mixing C + fortran.         character c print *,'Press return key ' i=fget(c) print *,'Bye' end --------------------------------------------------------------------------------
Sat, 18 Sep 2010 19:28:03 GMT
Gerry For #23 / 30	Press any key to continue? Quote: >>> There's been so much discussion on my original post, but in the end, >>> the answer is simply, it can't be done in Fortran. Thanks for all the >>> suggestions though. >> It can be done in fortran, if only by binding C: >> #include <stdio.h> >> int main(void) >> { >> int ch = '*'; >> ++ ch; >> putchar(ch); >> putchar('\n'); >> printf ("Press carriage return\n"); >> getchar(); >> } >> // gcc -o plus plus.c >> This program displays a plus and hangs around because of the getchar >> call. I believe that the printf is the only thing that can't be bound >> here. >> system ("pause"); >> is another one to remember.  Pause is something windows understands, if >> that's your game. > You missed the point, as did I at first. He wants the user to be able to > press "any" key, not just the "return" key. I feel unusually qualified as furunculus, inventor of the 'any' key. Quote: > Btw, if "return" key is good enough, you could use the fget intrinsic > supplied by g77, no need for mixing C + fortran. >        character c >        print *,'Press return key ' >        i=fget(c) >        print *,'Bye' >        end > ------------ -------------- ------------- ------------- -------------- -------------- ... thinking about this. -- "That this social order with its pauperism, famines, prisons, gallows, armies, and wars is necessary to society; that still greater disaster would ensue if this organization were destroyed; all this is said only by those who profit by this organization, while those who suffer from it - and they are ten times as numerous - think and say quite the contrary." ~~  Leo Tolstoy
Sat, 18 Sep 2010 21:08:49 GMT
Gordon Sand #24 / 30	Press any key to continue? Quote: >> There's been so much discussion on my original post, but in the end, >> the answer is simply, it can't be done in Fortran. Thanks for all the >> suggestions though. > Basically, that's right. There can sometimes be system-dependent ways > that might be acessible from Fortran, but it can't be done directly "in > Fortran". > Which makes it even more puzzling why such a translation would be > assigned as part of a homework. Translating something from Basic to > Fortran (particularly an old version of Fortran) seems like an odd > homework problem in the first place. It wouldn't fit well in a typival > Fortran class (because of the assumption that you know Basic). It would > fit even less well in a typical Basic class. It seems even more odd when > it is something that can't properly be translated. I suppose it could > possibly be intended as an illustration of language diferences, but it > would be a rather "{*filter*}" approach to assign an "impossible" homework > problem and let you figure out that it is impossible. I've seen profs do > things like that, but it isn't common. In an undergraduate course on differetnial equations there was an exam with a solve 4 of 10 differential equations as one of the problems. More than 4 were easy and a few were "well known" to be difficult or worse. The explanation was that part of the training was to know what you could not do. It was an explanaton that stopped the complaints about an overly difficult exam. I only learned later that the prof was a renowned expert on black holes and a student of Schrodinger. Quote: > It leads one to suspect more mundane explanations. I once had students do the same problem 3 times but with systems of differing level of abstraction. The purpose was to illustrate the low level mechanics of the computation as well as the advantages of high level systems. The problem was to add 10 numbers so it was supposed to be simple. The course was intended to be about the culture of computing rather than any particlar language, system, etc.
Sat, 18 Sep 2010 20:55:06 GMT
Richard Mai #25 / 30	Press any key to continue? Quote: > You missed the point, as did I at first. He wants the user to be able to > press "any" key, not just the "return" key. > Btw, if "return" key is good enough, you could use the fget intrinsic > supplied by g77, no need for mixing C + fortran. If the return key were good enough, there would be no need for anything so special and system dependent either. A simple, portable, and standard-conforming   read(*,*) would be fine. As noted, that wasn't the OP's question. But I still had trouble letting such an esoteric answer pass when a much more straightforward one was available. -- Richard Maine                    | Good judgement comes from experience; email: last name at domain . net | experience comes from bad judgement. domain: summertriangle           |  -- Mark Twain
Sun, 19 Sep 2010 00:06:56 GMT
glen herrmannsfeld #26 / 30	Press any key to continue? (snip) Quote: > You missed the point, as did I at first. He wants the > user to be able to press "any" key, not just the "return" key. Sometimes you don't want "any key". In the beginning of MS-DOS when formatting disks it would ask "press any key to continue".  It seems that "any key" includes control-C.   This stayed at least until the early use of hard disk drives, and I knew someone whose hard disk was accidentally reformatted typing control-C to that prompt. -- glen
Sun, 19 Sep 2010 00:44:35 GMT
glen herrmannsfeld #27 / 30	Press any key to continue? (snip) Quote: > Which makes it even more puzzling why such a translation would be > assigned as part of a homework. Translating something from Basic to > Fortran (particularly an old version of Fortran) seems like an odd > homework problem in the first place. It wouldn't fit well in a typival > Fortran class (because of the assumption that you know Basic). It would > fit even less well in a typical Basic class. It seems even more odd when > it is something that can't properly be translated. I could imagine it as an introduction to parsing, before a real class on compiler theory, just to get students thinking about the problems of language translation. I did used to have a BNF description for HP BASIC and, before I had any books or class on compiler theory started to figure out how I would write a translator. -- glen
Sun, 19 Sep 2010 00:59:29 GMT
Luka Djiga #28 / 30	Press any key to continue? Quote: >You missed the point, as did I at first. He wants the user to be able to >press "any" key, not just the "return" key. Nope. He wants the user to press any key, not "any" key - when you write it within the parenthesis, you're assuming that there is a key labeled as such. :-) pozdrav dig
Sun, 19 Sep 2010 02:02:24 GMT
David Fran #29 / 30	Press any key to continue? Quote: > Sorry if this is a stupid question, but how do you do a "Press any key > to continue"? PAUSE will require you to type "go" while READ * > requires that you press the Enter key. My CVF compiler supports following... ! ----------------- program test use dflib write (*,*) 'wait until a key is pressed' do if ( peekcharqq() ) exit end do write (*,*) 'thank you, i needed that' end program
Sun, 19 Sep 2010 03:36:47 GMT
Bamm #30 / 30	Press any key to continue? Quote: > If the return key were good enough, there would be no need for anything > so special and system dependent either. A simple, portable, and > standard-conforming >   read(*,*) > would be fine. > As noted, that wasn't the OP's question. But I still had trouble letting > such an esoteric answer pass when a much more straightforward one was > available. True. And in fact, if you look at my original post, I was in fact looking for an alternative for read * because read * required an enter. So we now went a full circle. :)
Sun, 19 Sep 2010 10:30:40 GMT

Page 2 of 3

[ 30 post ]

Go to page: [1] [2] [3]

williamsonwhoseeps.blogspot.com

Source: http://computer-programming-forum.com/49-fortran/14e327a6c6ec9db8-2.htm

Share this post