AmiWest Lesson 3 - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:19:00Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

← Older revision		Revision as of 19:19, 26 January 2025
Line 5:		Line 5:
	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:		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>		<syntaxhighlight lang="C" line>
	IExec->DebugPrintF("my debug message\n");		IExec->DebugPrintF("my debug message\n");
	</syntaxhighlight>		</syntaxhighlight>

Steven Solie: /* GUI Input and Output */

2012-10-16T23:15:35Z

GUI Input and Output

← Older revision		Revision as of 23:15, 16 October 2012
Line 46:		Line 46:

	It is important to understand that each of the APIs above are not meant to be mixed especially on the same file at the same time. Although it is possible to mix APIs that doesn't mean it is a good idea and it will lead to less portable and less robust software.		It is important to understand that each of the APIs above are not meant to be mixed especially on the same file at the same time. Although it is possible to mix APIs that doesn't mean it is a good idea and it will lead to less portable and less robust software.

	== GUI Input and Output ==

	A word on text input/output here.

Steven Solie at 22:37, 16 October 2012

2012-10-16T22:37:53Z

← Older revision		Revision as of 22:37, 16 October 2012
Line 46:		Line 46:

	It is important to understand that each of the APIs above are not meant to be mixed especially on the same file at the same time. Although it is possible to mix APIs that doesn't mean it is a good idea and it will lead to less portable and less robust software.		It is important to understand that each of the APIs above are not meant to be mixed especially on the same file at the same time. Although it is possible to mix APIs that doesn't mean it is a good idea and it will lead to less portable and less robust software.

	== DOS Input and Output ==

	== GUI Input and Output ==		== GUI Input and Output ==

			A word on text input/output here.

Steven Solie: /* File Input and Output */

2012-10-16T22:35:48Z

File Input and Output

← Older revision		Revision as of 22:35, 16 October 2012
Line 35:		Line 35:
	== File Input and Output ==		== File Input and Output ==

	File input and output has many APIs to choose from. At the most basic level ~~you~~ have '''IDOS->Read()''' and '''IDOS->Write()'''.		File input and output has many APIs to choose from. At the most basic level we have '''IDOS->Read()''' and '''IDOS->Write()'''. These functions are simple unbuffered large data movers.

			Buffered data movers '''IDOS->FRead()''' and '''IDOS->FWrite()''' are also provided. Buffering is usually employed to batch together smaller data moves to more efficiently transfer them in larger chunks.

			When it comes to ISO C, you have '''fread()''' and '''fwrite()''' which can used to read and write data. These functions use buffering and you cannot make any assumptions regarding how they are buffered. Underneath, they will ultimately call the DOS functions mentioned above.

			The UNIX operating system also defines a common set of input and output functions based on '''read()''' and '''write()'''. The behaviour of these functions is governed by the POSIX standard and not ISO C. Given the popularity of UNIX, these functions are also provided by the C libraries used on AmigaOS. Again, they ultimately will call the DOS functions mentioned above.

			Although each of these APIs are essentially independent, they also allow for programmers to convert from one API to the other. For example, the '''fileno()''' function will return the POSIX file handle for a ISO C stream. The clib2 function '''__get_default_file()''' allows access to the underlying BPTR pointer from DOS.

			It is important to understand that each of the APIs above are not meant to be mixed especially on the same file at the same time. Although it is possible to mix APIs that doesn't mean it is a good idea and it will lead to less portable and less robust software.

	== DOS Input and Output ==		== DOS Input and Output ==

Steven Solie: /* Console Input and Output */

2012-10-16T22:09:37Z

Console Input and Output

← Older revision		Revision as of 22:09, 16 October 2012
Line 31:		Line 31:
	The C startup code will auto-magically create these standard streams for you and assign them to the DOS-provided streams mentioned above.		The C startup code will auto-magically create these standard streams for you and assign them to the DOS-provided streams mentioned above.

	Whether you use '''printf()''' or '''IDOS->Printf()''' they will both ultimately end up using the Output stream. However, this doesn't mean you can just mix and match to taste. The reason is that each of these calls are buffered. The C library could use its own buffering or it could depend on DOS buffering. Programmers should not assume one or the other and instead should be consistent in their choice of API.		Whether you use '''printf()''' or '''IDOS->Printf()''' they will both ultimately end up using the DOS Output stream. However, this doesn't mean you can just mix and match to taste. The reason is that each of these calls are buffered. The C library could use its own buffering or it could depend on DOS buffering. Programmers should not assume one or the other and instead should be consistent in their choice of API.

	== File Input and Output ==		== File Input and Output ==

Steven Solie: /* Console Input and Output */

2012-10-16T22:07:48Z

Console Input and Output

← Older revision		Revision as of 22:07, 16 October 2012
Line 31:		Line 31:
	The C startup code will auto-magically create these standard streams for you and assign them to the DOS-provided streams mentioned above.		The C startup code will auto-magically create these standard streams for you and assign them to the DOS-provided streams mentioned above.

	Whether you use ''printf()'' or ''IDOS->Printf()'' they will both ultimately end up using the Output stream. However, this doesn't mean you can just mix and match to taste. The reason is that each of these calls are buffered. The C library could use its own buffering or it could depend on DOS buffering. Programmers should not assume one or the other and instead should be consistent in their choice of API ~~to use~~.		Whether you use '''printf()''' or '''IDOS->Printf()''' they will both ultimately end up using the Output stream. However, this doesn't mean you can just mix and match to taste. The reason is that each of these calls are buffered. The C library could use its own buffering or it could depend on DOS buffering. Programmers should not assume one or the other and instead should be consistent in their choice of API.

	=== printf() and scanf() ===


			== File Input and Output ==

			File input and output has many APIs to choose from. At the most basic level you have '''IDOS->Read()''' and '''IDOS->Write()'''.

	== DOS Input and Output ==		== DOS Input and Output ==

Steven Solie: /* AmiWest Lesson 3: Input and Output */

2012-10-16T22:05:37Z

AmiWest Lesson 3: Input and Output

@@ Line 13: / Line 13: @@
 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 ==
+== Console Input and Output ==
 == DOS Input and Output ==

Steven Solie at 21:38, 16 October 2012

2012-10-16T21:38:25Z

← Older revision		Revision as of 21:38, 16 October 2012
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 ==

Steven Solie: Created page with "= AmiWest Lesson 3: Input and Output = == Debug Output == == Shell Input and Output == == DOS Input and Output == == GUI Input and Output =="

2012-10-10T04:06:10Z

Created page with "= AmiWest Lesson 3: Input and Output = == Debug Output == == Shell Input and Output == == DOS Input and Output == == GUI Input and Output =="

New page

= AmiWest Lesson 3: Input and Output =

== Debug Output ==

== Shell Input and Output ==

== DOS Input and Output ==

== GUI Input and Output ==