Source:NetHack 3.4.3/src/cmd.c - Revision history

Furey: Fix instructions for linking to a particular line. Current instructions incorrectly link to a different version of NetHack.

2024-06-24T06:48:08Z

Fix instructions for linking to a particular line. Current instructions incorrectly link to a different version of NetHack.

Umbire the Phantom: remove MSH, captialize Wikipedia

2024-06-21T02:15:32Z

remove MSH, captialize Wikipedia

Furey: /* readchar */ send some redlinks to wikipedia: "standard input", "SYSV"

2024-06-18T13:59:51Z

‎readchar: send some redlinks to wikipedia: "standard input", "SYSV"

Furey: Delinkify "event". Fixes a redlink.

2024-06-16T22:50:52Z

Delinkify "event". Fixes a redlink.

Blackcustard: /* cmdlist */ Described cmdlist array.

2011-07-16T15:58:36Z

‎cmdlist: Described cmdlist array.

Paxedbot: moved Source:Cmd.c to Source:NetHack 3.4.3/src/cmd.c: Moving src to subdirs

2011-01-31T19:20:57Z

moved Source:Cmd.c to Source:NetHack 3.4.3/src/cmd.c: Moving src to subdirs

Paxedbot: Adding MIXEDSYNTAXHIGHLIGHT

2010-11-20T18:53:23Z

Adding __MIXEDSYNTAXHIGHLIGHT__

Kernigh bot: Cmd.c moved to Source:Cmd.c: Robot: moved page

2008-03-03T21:31:53Z

Cmd.c moved to Source:Cmd.c: Robot: moved page

Kernigh: /* readchar */ I noticed something strange in the code here, so I decided to annotate this function. "readchar" retrieves key events (or mouse clicks converted to queued key events).

2007-05-26T20:08:28Z

‎readchar: I noticed something strange in the code here, so I decided to annotate this function. "readchar" retrieves key events (or mouse clicks converted to queued key events).

Paxed: /* isok */

2007-03-25T17:40:23Z

‎isok

← Older revision		Revision as of 06:48, 24 June 2024
Line 1:		Line 1:
−	Below is the full text to src/cmd.c from NetHack 3.4.3. To link to a particular line, write [[~~cmd~~.~~c#line123\|<nowiki>[[~~cmd.c#line123~~]]</nowiki>~~]], for example.	+	Below is the full text to src/cmd.c from NetHack 3.4.3. To link to a particular line, write [[Source:NetHack 3.4.3/src/cmd.c#line123]], for example.

	== Top of file ==		== Top of file ==

@@ Line 1: / Line 1: @@
 Below is the full text to src/cmd.c from NetHack 3.4.3. To link to a particular line, write [[cmd.c#line123|<nowiki>[[cmd.c#line123]]</nowiki>]], for example.
@@ Line 2,637: / Line 2,636: @@
   <span id="line2448">2448. </span>
-The C language ''getchar'' function waits for a character on the [[wikipedia:standard input|standard input]] and use it. Though the [[tty]] window port could use ''getchar'' to access keyboard events, the other window ports must use different mechanisms, like [[X11]] events or [[Qt]] signals.
+The C language ''getchar'' function waits for a character on the [[Wikipedia:standard input|standard input]] and use it. Though the [[tty]] window port could use ''getchar'' to access keyboard events, the other window ports must use different mechanisms, like [[X11]] events or [[Qt]] signals.
 Thus, the [[DevTeam]] now uses a ''Getchar'' macro (starting with an uppercase G). This macro calls a window-port-specific function to grab the key. Thus the ''Getchar'' macro takes the place of the ''getchar'' function that NetHack used when it was a tty-only game.
-Given this, it seems strange that the NR_OF_EOFS code is here. On a [[wikipedia:SYSV|SYSV]] system, NR_OF_EOFS became 20 at [[cmd.c#line14]]. This crude hack attempts to distinguish a permanent end-of-file (EOF) from a temporary interruption  by re-reading the character 20 times. (The more correct way to do this would be to check the global ''errno'' variable for the EINTR error from the [[Unix]] ''read'' system call.) The strange situation is that this hack calls <tt>clearerr(stdin)</tt> even if standard input is not the source of our key events. It would be reasonable to move this code to the [[tty]]-specific implementation of the ''Getchar'' function.
+Given this, it seems strange that the NR_OF_EOFS code is here. On a [[Wikipedia:SYSV|SYSV]] system, NR_OF_EOFS became 20 at [[cmd.c#line14]]. This crude hack attempts to distinguish a permanent end-of-file (EOF) from a temporary interruption  by re-reading the character 20 times. (The more correct way to do this would be to check the global ''errno'' variable for the EINTR error from the [[Unix]] ''read'' system call.) The strange situation is that this hack calls <tt>clearerr(stdin)</tt> even if standard input is not the source of our key events. It would be reasonable to move this code to the [[tty]]-specific implementation of the ''Getchar'' function.
 Other than calling ''Getchar'', the ''readchar'' function also needs to worry about mouse clicks from window ports that support them. It deals with them by calling the ''click_to_cmd'' function to translate the mouse click into equivalent key events. It then stores the key characters in the <tt>readchar_queue</tt>. Until this queue is empty, subsequent calls to ''readchar'' use this queue instead of requesting another event from ''Getchar''.

@@ Line 2,637: / Line 2,637: @@
   <span id="line2448">2448. </span>
-The C language ''getchar'' function waits for a character on the [[standard input]] and use it. Though the [[tty]] window port could use ''getchar'' to access keyboard events, the other window ports must use different mechanisms, like [[X11]] events or [[Qt]] signals.
+The C language ''getchar'' function waits for a character on the [[wikipedia:standard input|standard input]] and use it. Though the [[tty]] window port could use ''getchar'' to access keyboard events, the other window ports must use different mechanisms, like [[X11]] events or [[Qt]] signals.
 Thus, the [[DevTeam]] now uses a ''Getchar'' macro (starting with an uppercase G). This macro calls a window-port-specific function to grab the key. Thus the ''Getchar'' macro takes the place of the ''getchar'' function that NetHack used when it was a tty-only game.
-Given this, it seems strange that the NR_OF_EOFS code is here. On a [[SYSV]] system, NR_OF_EOFS became 20 at [[cmd.c#line14]]. This crude hack attempts to distinguish a permanent end-of-file (EOF) from a temporary interruption  by re-reading the character 20 times. (The more correct way to do this would be to check the global ''errno'' variable for the EINTR error from the [[Unix]] ''read'' system call.) The strange situation is that this hack calls <tt>clearerr(stdin)</tt> even if standard input is not the source of our key events. It would be reasonable to move this code to the [[tty]]-specific implementation of the ''Getchar'' function.
+Given this, it seems strange that the NR_OF_EOFS code is here. On a [[wikipedia:SYSV|SYSV]] system, NR_OF_EOFS became 20 at [[cmd.c#line14]]. This crude hack attempts to distinguish a permanent end-of-file (EOF) from a temporary interruption  by re-reading the character 20 times. (The more correct way to do this would be to check the global ''errno'' variable for the EINTR error from the [[Unix]] ''read'' system call.) The strange situation is that this hack calls <tt>clearerr(stdin)</tt> even if standard input is not the source of our key events. It would be reasonable to move this code to the [[tty]]-specific implementation of the ''Getchar'' function.
 Other than calling ''Getchar'', the ''readchar'' function also needs to worry about mouse clicks from window ports that support them. It deals with them by calling the ''click_to_cmd'' function to translate the mouse click into equivalent key events. It then stores the key characters in the <tt>readchar_queue</tt>. Until this queue is empty, subsequent calls to ''readchar'' use this queue instead of requesting another event from ''Getchar''.

@@ Line 2,590: / Line 2,590: @@
 == readchar ==
-The ''readchar'' function waits for an [[event]] from the [[keyboard]] and returns the next character typed by a user. NetHack has many reasons to need to wait for your [[command]]: you might on the [[map]], at a [[menu]], at a "-- More --" prompt, or elsewhere. The ''readchar'' functions acts as a gate through which all of these places obtain your instruction. Most of the calls to ''readchar'' are elsewhere in cmd.c, though two are in [[invent.c]].
+The ''readchar'' function waits for an event from the [[keyboard]] and returns the next character typed by a user. NetHack has many reasons to need to wait for your [[command]]: you might on the [[map]], at a [[menu]], at a "-- More --" prompt, or elsewhere. The ''readchar'' functions acts as a gate through which all of these places obtain your instruction. Most of the calls to ''readchar'' are elsewhere in cmd.c, though two are in [[invent.c]].
   <span id="line2405">2405. #ifdef OVL0</span>

@@ Line 1,456: / Line 1,456: @@
 == cmdlist ==
   <span id="line1345">1345. #ifdef OVL1</span>
   <span id="line1346">1346. </span>

← Older revision	Revision as of 19:20, 31 January 2011
(No difference)

← Older revision		Revision as of 18:53, 20 November 2010
Line 1:		Line 1:
		+	__MIXEDSYNTAXHIGHLIGHT__
	Below is the full text to src/cmd.c from NetHack 3.4.3. To link to a particular line, write [[cmd.c#line123\|<nowiki>[[cmd.c#line123]]</nowiki>]], for example.		Below is the full text to src/cmd.c from NetHack 3.4.3. To link to a particular line, write [[cmd.c#line123\|<nowiki>[[cmd.c#line123]]</nowiki>]], for example.

← Older revision	Revision as of 21:31, 3 March 2008
(No difference)

@@ Line 2,588: / Line 2,588: @@
 == readchar ==
   <span id="line2405">2405. #ifdef OVL0</span>
@@ Line 2,633: / Line 2,634: @@
   <span id="line2447">2447. }</span>
   <span id="line2448">2448. </span>
 == dotravel ==

← Older revision		Revision as of 17:40, 25 March 2007
Line 2,373:		Line 2,373:

	== isok ==		== isok ==
		+
		+	<tt>isok()</tt> takes two parameters, x and y coordinate, and returns 1 if the coordinate (x,y) is inside the map area, 0 otherwise.

	<span id="line2204">2204. #ifdef OVL0</span>		<span id="line2204">2204. #ifdef OVL0</span>