Programming in the Amiga Environment - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:09:48Z

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

← Older revision		Revision as of 19:09, 26 January 2025
Line 38:		Line 38:
	Almost any program you write for the Amiga will have to call the OpenLibrary() and GetInterface() functions. Usage is as follows:		Almost any program you write for the Amiga will have to call the OpenLibrary() and GetInterface() functions. Usage is as follows:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	// Global: declare this above main()		// Global: declare this above main()
	struct Library *LibBase;		struct Library *LibBase;
Line 148:		Line 148:
	Here's a brief example showing how OpenLibrary() and GetInterface() are used in C.		Here's a brief example showing how OpenLibrary() and GetInterface() are used in C.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	/* easy.c: a complete example of how to open an Amiga function library in C.		/* easy.c: a complete example of how to open an Amiga function library in C.
	* In this case the function library is Intuition. Once the Intuition		* In this case the function library is Intuition. Once the Intuition

Daniel Jedlicka: Fixed a typo.

2016-03-20T19:00:24Z

Fixed a typo.

← Older revision		Revision as of 19:00, 20 March 2016
Line 306:		Line 306:
	* Never access shared data structures directly without the proper mutual exclusion (locking). Remember that other tasks may be accessing the same structures.		* Never access shared data structures directly without the proper mutual exclusion (locking). Remember that other tasks may be accessing the same structures.

	* The system does not monitor the size of a ~~program‚Äôs~~ stack. (Your compiler may have an option to do this for you.) Take care that your program does not cause stack overflow and provide extra stack space for the possibility that some functions may use up additional stack space in future versions of the OS.		* The system does not monitor the size of a program's stack. (Your compiler may have an option to do this for you.) Take care that your program does not cause stack overflow and provide extra stack space for the possibility that some functions may use up additional stack space in future versions of the OS.

	* Never use a polling loop to test signal bits. If your program waits for external events like menu selection or keystrokes, do not bog down the multitasking system by busy-waiting in a loop. Instead, let your task go to sleep by ''Wait()''ing on its signal bits. For example:		* Never use a polling loop to test signal bits. If your program waits for external events like menu selection or keystrokes, do not bog down the multitasking system by busy-waiting in a loop. Instead, let your task go to sleep by ''Wait()''ing on its signal bits. For example:

Lyle Hazelwood: /* Libraries of functions */ minor edit in code example, replace "if(LibIFace)" with "if(LibBase)", added CloseLibrary() if GetInterface() failed

2013-12-27T17:17:16Z

Libraries of functions: minor edit in code example, replace "if(LibIFace)" with "if(LibBase)", added CloseLibrary() if GetInterface() failed

← Older revision		Revision as of 17:17, 27 December 2013
Line 46:		Line 46:
	{		{
	LibBase = IExec->OpenLibrary("library.name", libversion);		LibBase = IExec->OpenLibrary("library.name", libversion);
	if(~~LibIFace~~ == NULL)		if(LibBase == NULL)
	{		{
	// Library did not open, so exit.		// Library did not open, so exit.
Line 55:		Line 55:
	if(LibIFace == NULL)		if(LibIFace == NULL)
	{		{
			IExec->CloseLibrary(LibBase);
	// Could not get Interface, so exit.		// Could not get Interface, so exit.
	}		}

Philippe Ferrucci: /* Two Kinds of Memory */

2013-08-03T18:07:37Z

Two Kinds of Memory

← Older revision		Revision as of 18:07, 3 August 2013
Line 257:		Line 257:

	{\| class="wikitable"		{\| class="wikitable"
	\| ''What Every Amiga Programmer Should Know'': The Amiga has ''two'' kinds of memory: ''Chip'' memory and ''Fast'' memory. Use the right kind.		\| ''What Every Amiga Programmer Should Know'': The Classic Amiga has ''two'' kinds of memory: ''Chip'' memory and ''Fast'' memory. Use the right kind.
	\|}		\|}

Steven Solie: /* About Release 4 */

2013-01-17T21:55:22Z

About Release 4

← Older revision		Revision as of 21:55, 17 January 2013
Line 248:		Line 248:
	Release 4 first appeared on the ''AmigaOne XE''. This initial version corresponds to Kickstart 4.0, system library version number V50.		Release 4 first appeared on the ''AmigaOne XE''. This initial version corresponds to Kickstart 4.0, system library version number V50.

		⚫	{{Note\|title=What Every Amiga Programmer Should Know\|text=Some libraries or specific functions are not available in older versions of the Amiga operating system. Be sure to ask for the lowest library version that meets the requirements of your program.}}
	{\| class="wikitable"
⚫	\|''What Every Amiga Programmer Should Know~~'':~~ Some libraries or specific functions are not available in older versions of the Amiga operating system. Be sure to ask for the lowest library version that meets the requirements of your program.
	\|}

	==== Two Kinds of Memory ====		==== Two Kinds of Memory ====

Steven Solie: /* Exec: The System Executive */

2013-01-17T21:54:41Z

Exec: The System Executive

← Older revision		Revision as of 21:54, 17 January 2013
Line 228:		Line 228:
	The diagram above shows how the entire Amiga operating system is built as a tree starting at SysBase. [[Exec]] keeps linked lists of all the system libraries, devices, memory, tasks and other data structures. Each of these in turn can have its own variables and linked lists of data structures built onto it. In this way, the flexibility of the OS is preserved so that upgrades can be made without jeopardizing compatibility.		The diagram above shows how the entire Amiga operating system is built as a tree starting at SysBase. [[Exec]] keeps linked lists of all the system libraries, devices, memory, tasks and other data structures. Each of these in turn can have its own variables and linked lists of data structures built onto it. In this way, the flexibility of the OS is preserved so that upgrades can be made without jeopardizing compatibility.

		⚫	{{Note\|title=What Every Amiga Programmer Should Know\|text=The Amiga has a dynamic memory map. There are no fixed locations for operating system variables and routines. Do not call ROM routines or access system data structures directly. Instead use the indirect access methods provided by the system.}}
	{\| class="wikitable"
	\|-
⚫	\| ''What Every Amiga Programmer Should Know~~:''~~ The Amiga has a dynamic memory map. There are no fixed locations for operating system variables and routines. Do not call ROM routines or access system data structures directly. Instead use the indirect access methods provided by the system.
	\|}

	=== Operating system versions ===		=== Operating system versions ===

Steven Solie: /* Libraries, Devices and Resources */

2013-01-17T21:54:06Z

Libraries, Devices and Resources

← Older revision		Revision as of 21:54, 17 January 2013
Line 202:		Line 202:
	Devices and resources are managed by [[Exec]] just as libraries are. For more information on devices and resources, see the respective sections.		Devices and resources are managed by [[Exec]] just as libraries are. For more information on devices and resources, see the respective sections.

		⚫	{{Note\|title=What Every Amiga Programmer Should Know\|text=The functions in the Amiga OS are accessed through shared run-time libraries. Libraries must be opened before their functions may be used. The system's master library, [[Exec]], is always open. The [[Exec]] function OpenLibrary() is used to open all other libraries.}}
	{\| class="wikitable"
⚫	\| ''What Every Amiga Programmer Should Know~~'':~~ The functions in the Amiga OS are accessed through shared run-time libraries. Libraries must be opened before their functions may be used. The system's master library, [[Exec]], is always open. The [[Exec]] function OpenLibrary() is used to open all other libraries.
	\|}

	=== Dynamic memory architecture ===		=== Dynamic memory architecture ===

Steven Solie: /* What the System Doesn't Do For You */

2013-01-17T21:53:32Z

What the System Doesn't Do For You

← Older revision		Revision as of 21:53, 17 January 2013
Line 28:		Line 28:
	In fact, Amiga programmers need to be careful with every system resource, not just memory. All system resources from audio channels to the floppy disk drives are shared among tasks. Before using a resource, you must ask the system for access to the resource. This may fail if the resource is already being used by another task. Once you have control of a resource, no other task can use it, so give it up as soon as you are finished. When your program exits, you must give everything back whether it's memory, access to a file, or an I/O port. You are responsible for this, the system will not do it for you automatically.		In fact, Amiga programmers need to be careful with every system resource, not just memory. All system resources from audio channels to the floppy disk drives are shared among tasks. Before using a resource, you must ask the system for access to the resource. This may fail if the resource is already being used by another task. Once you have control of a resource, no other task can use it, so give it up as soon as you are finished. When your program exits, you must give everything back whether it's memory, access to a file, or an I/O port. You are responsible for this, the system will not do it for you automatically.

		⚫	{{Note\|title=What Every Amiga Programmer Should Know\|text=The Amiga is a ''multitasking'' computer. Keep in mind that other tasks are running at the same time as your application. Always ask the system for control of any resource you need; some other task may already be using it. Give it back as soon as you are done; another task may want to use it. This applies to just about every computing activity your application can perform.}}
	{\| class="wikitable"
⚫	\| ''What Every Amiga Programmer Should Know~~'':~~ The Amiga is a ''multitasking'' computer. Keep in mind that other tasks are running at the same time as your application. Always ask the system for control of any resource you need; some other task may already be using it. Give it back as soon as you are done; another task may want to use it. This applies to just about every computing activity your application can perform.
	\|}

	=== Libraries of functions ===		=== Libraries of functions ===

Philippe Ferrucci: /* AmigaOS Interface Style Guide */

2012-06-21T21:10:42Z

AmigaOS Interface Style Guide

← Older revision		Revision as of 21:10, 21 June 2012
Line 376:		Line 376:

	While the look of windows and gadgets can be changed by the user, the default look is similar to this:		While the look of windows and gadgets can be changed by the user, the default look is similar to this:

	[[File:About.png]]		[[File:About.png]]

Philippe Ferrucci: /* AmigaOS Interface Style Guide */

2012-06-21T21:10:23Z

AmigaOS Interface Style Guide

← Older revision		Revision as of 21:10, 21 June 2012
Line 374:		Line 374:
	In order to make all programs in AmigaOS look consistent, AmigaOS provides some default thumbnails that developers must use in their GUI. These pictures are located in the '''tbimages:''' assign. They are installed in any AmigaOS installation.		In order to make all programs in AmigaOS look consistent, AmigaOS provides some default thumbnails that developers must use in their GUI. These pictures are located in the '''tbimages:''' assign. They are installed in any AmigaOS installation.
	Note that something may still go wrong and these pictures may not be found. In this case, the program must provide a fallback method instead of just failing. The developer can choose to display text-only toolbars or include default pictures with their program.		Note that something may still go wrong and these pictures may not be found. In this case, the program must provide a fallback method instead of just failing. The developer can choose to display text-only toolbars or include default pictures with their program.

			While the look of windows and gadgets can be changed by the user, the default look is similar to this:
			[[File:About.png]]

	== Error Reports ==		== Error Reports ==