Copyright (c) Hyperion Entertainment and contributors.
Difference between revisions of "AmiWest Lesson 3"
Jump to navigation
Jump to search
Steven Solie (talk | contribs) (Created page with "= AmiWest Lesson 3: Input and Output = == Debug Output == == Shell Input and Output == == DOS Input and Output == == GUI Input and Output ==") |
Steven Solie (talk | contribs) |
||
Line 2: | Line 2: | ||
== Debug Output == |
== Debug Output == |
||
+ | |||
+ | One of the first things you will need is some way to output text for debugging purposes. Exec has a simple function which is provided for this purpose and it is used as follows: |
||
+ | |||
+ | <syntaxhighlight> |
||
+ | IExec->DebugPrintF("my debug message\n"); |
||
+ | </syntaxhighlight> |
||
+ | |||
+ | The text may go to the default serial port, a debug buffer or even a console window via a tool called Sashimi. |
||
+ | |||
+ | More information about this debugging facility can be found at [[Debug_Logging_on_AmigaOS|Debug Logging]] and [[Redirecting_Debug_Output_to_the_Serial_Port_on_Startup|Redirecting Debug Output]]. |
||
== Shell Input and Output == |
== Shell Input and Output == |
Revision as of 22:38, 16 October 2012
Contents
AmiWest Lesson 3: Input and Output
Debug Output
One of the first things you will need is some way to output text for debugging purposes. Exec has a simple function which is provided for this purpose and it is used as follows:
IExec->DebugPrintF("my debug message\n");
The text may go to the default serial port, a debug buffer or even a console window via a tool called Sashimi.
More information about this debugging facility can be found at Debug Logging and Redirecting Debug Output.