Newlib Library - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:23:08Z

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

← Older revision		Revision as of 19:23, 26 January 2025
Line 9:		Line 9:
	The standard C startup code provides information on whether your application was launched from Workbench, Shell console or as a file system. Your program always starts using the standard '''argc''' and '''argv''' parameters but they are interpreted differently depending on how it was started.		The standard C startup code provides information on whether your application was launched from Workbench, Shell console or as a file system. Your program always starts using the standard '''argc''' and '''argv''' parameters but they are interpreted differently depending on how it was started.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	int main(int argc, char **argv)		int main(int argc, char **argv)
	</syntaxhighlight>		</syntaxhighlight>
Line 17:		Line 17:
	The '''argc''' argument is equal to zero. The '''argv''' argument is a pointer to a struct WBStartup.		The '''argc''' argument is equal to zero. The '''argv''' argument is a pointer to a struct WBStartup.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	#include <workbench/startup.h>		#include <workbench/startup.h>

Line 39:		Line 39:
	If '''argc''' is greater than zero then it means the application was started from the Shell console and the normal C startup rules apply.		If '''argc''' is greater than zero then it means the application was started from the Shell console and the normal C startup rules apply.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	int main(int argc, char **argv)		int main(int argc, char **argv)
	{		{
Line 56:		Line 56:
	If '''argc''' is -1 then means the application was started as a file system. This special option should only be used by file systems.		If '''argc''' is -1 then means the application was started as a file system. This special option should only be used by file systems.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	#include <dos/dosextens.h>		#include <dos/dosextens.h>

Line 107:		Line 107:
	=== Options ===		=== Options ===

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	extern const char *__stdiowin;		extern const char *__stdiowin;
	</syntaxhighlight>		</syntaxhighlight>
Line 113:		Line 113:
	Define '''__stdiowin''' to control the default standard I/O window which will open automatically if your program needs it. The default is "CON:64/48/800/200/[CLI command name\|Task name]/AUTO/CLOSE/WAIT".		Define '''__stdiowin''' to control the default standard I/O window which will open automatically if your program needs it. The default is "CON:64/48/800/200/[CLI command name\|Task name]/AUTO/CLOSE/WAIT".

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	extern int __unix_path_semantics;		extern int __unix_path_semantics;
	</syntaxhighlight>		</syntaxhighlight>
Line 123:		Line 123:

	The following is an example program which demonstrates the feature.		The following is an example program which demonstrates the feature.
	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	#include <proto/dos.h>		#include <proto/dos.h>
	#include <stdio.h>		#include <stdio.h>

Frédéric Khannouf: Small correction in the last Shared Interface Pointer sentence.

2020-07-05T13:34:41Z

Small correction in the last Shared Interface Pointer sentence.

← Older revision		Revision as of 13:34, 5 July 2020
Line 3:		Line 3:
	== Shared Interface Pointer ==		== Shared Interface Pointer ==

	Newlib is a rather unique in that it uses a shared interface pointer name INewlib (struct Interface* type). This is only a concern when you are not using the standard C startup code and opening newlib.library directly. One consequence of using a shared interface pointer is that you must specify the NP_Child tag when using IDOS->CreateNewProc() if ~~you~~ child process is to share the parent process' newlib context information (e.g. stdin, stdout and stderr).		Newlib is a rather unique in that it uses a shared interface pointer name INewlib (struct Interface* type). This is only a concern when you are not using the standard C startup code and opening newlib.library directly. One consequence of using a shared interface pointer is that you must specify the NP_Child tag when using IDOS->CreateNewProc() if your child process is going to share the parent process' newlib context information (e.g. stdin, stdout and stderr).

	== Startup Code ==		== Startup Code ==

Steven Solie: /* File System */

2016-11-17T19:35:50Z

File System

← Older revision		Revision as of 19:35, 17 November 2016
Line 74:		Line 74:
	{		{
	// Reply to the startup packet before entering main loop.		// Reply to the startup packet before entering main loop.
	if ~~(msg !~~= ~~NULL)~~		pkt->dp_Res1 = DOSTRUE;
	{		pkt->dp_Res2 = 0;
	pkt->~~dp_Res1 =~~ ~~DOSTRUE~~;		IExec->PutMsg(pkt->dp_Port, msg);
⚫	pkt->dp_Res2 = 0;
	IExec->PutMsg(pkt->dp_Port, msg);
	}

	// File system main loop.		// File system main loop.
Line 89:		Line 86:
	{		{
	// File system failed to initialize so return a DOS error code.		// File system failed to initialize so return a DOS error code.
	if ~~(msg !~~= ~~NULL)~~		pkt->dp_Res1 = DOSFALSE;
		⚫	pkt->dp_Res2 = ERROR_NO_FREE_STORE;
	{
	pkt->~~dp_Res1 =~~ ~~DOSFALSE~~;		IExec->PutMsg(pkt->dp_Port, msg);

	pkt->dp_Res2 = ERROR_NO_FREE_STORE;
		⚫	result = RETURN_FAIL;
	IExec->PutMsg(pkt->dp_Port, msg);
⚫	result = RETURN_FAIL;
	}
	}		}
	}		}

Steven Solie: /* File System */

2016-11-17T16:55:35Z

File System

← Older revision		Revision as of 16:55, 17 November 2016
Line 57:		Line 57:

	<syntaxhighlight>		<syntaxhighlight>
			#include <dos/dosextens.h>

	int main(int argc, char **argv)		int main(int argc, char **argv)
	{		{
			int result;

	if (argc == -1)		if (argc == -1)
	{		{
Line 64:		Line 68:
	struct Message *msg = pkt->dp_Link;		struct Message *msg = pkt->dp_Link;

	// File system ~~processing loop~~.		// File system initialization.
			BOOL initialized = file_system_init(msg);
⚫	...

	if (~~msg != NULL~~)		if (initialized)
			{
			// Reply to the startup packet before entering main loop.
			if (msg != NULL)
			{
			pkt->dp_Res1 = DOSTRUE;
			pkt->dp_Res2 = 0;
			IExec->PutMsg(pkt->dp_Port, msg);
			}

			// File system main loop.
		⚫	...

			result = RETURN_OK;
			}
			else
	{		{
			// File system failed to initialize so return a DOS error code.
	struct MsgPort *replyport = pkt->dp_Port;
	~~pkt->dp_Res1~~ = ~~DOSTRUE;~~		if (msg != NULL)
	~~pkt->dp_Res2 = 0;~~		{
	~~IExec~~->~~PutMsg(replyport,~~ ~~msg)~~;		pkt->dp_Res1 = DOSFALSE;
			pkt->dp_Res2 = ERROR_NO_FREE_STORE;
			IExec->PutMsg(pkt->dp_Port, msg);
			result = RETURN_FAIL;
			}
	}		}
	}		}

	return 0;		return result;
	}		}
	</syntaxhighlight>		</syntaxhighlight>

Steven Solie: /* Startup Code */

2016-11-17T03:28:54Z

Startup Code

@@ Line 7: / Line 7: @@
 == Startup Code ==
-The standard C startup code provides information on whether your application was launched from Workbench or the Shell console. Your program always starts using the standard '''argc''' and '''argv''' parameters:
+The standard C startup code provides information on whether your application was launched from Workbench, Shell console or as a file system. Your program always starts using the standard '''argc''' and '''argv''' parameters but they are interpreted differently depending on how it was started.
 <syntaxhighlight>
@@ Line 13: / Line 13: @@
 </syntaxhighlight>
 === Standard Interfaces ===

Philippe Ferrucci: /* Shared Interface Pointer */

2013-03-08T11:29:46Z

Shared Interface Pointer

← Older revision		Revision as of 11:29, 8 March 2013
Line 3:		Line 3:
	== Shared Interface Pointer ==		== Shared Interface Pointer ==

	Newlib is a rather unique in that is uses a shared interface pointer name INewlib (struct Interface* type). This is only a concern when you are not using the standard C startup code and opening newlib.library directly. One consequence of using a shared interface pointer is that you must specify the NP_Child tag when using IDOS->CreateNewProc() if you child process is to share the parent process' newlib context information (e.g. stdin, stdout and stderr).		Newlib is a rather unique in that it uses a shared interface pointer name INewlib (struct Interface* type). This is only a concern when you are not using the standard C startup code and opening newlib.library directly. One consequence of using a shared interface pointer is that you must specify the NP_Child tag when using IDOS->CreateNewProc() if you child process is to share the parent process' newlib context information (e.g. stdin, stdout and stderr).

	== Startup Code ==		== Startup Code ==

Steven Solie: /* Startup Code */

2013-03-08T05:11:31Z

Startup Code

← Older revision		Revision as of 05:11, 8 March 2013
Line 36:		Line 36:
	</syntaxhighlight>		</syntaxhighlight>
	Define to 1 to enable POSIX style path semantics which is useful when porting applications from UNIX.		Define to 1 to enable POSIX style path semantics which is useful when porting applications from UNIX.

			== DOS File Handles ==

			Sometimes the underlying DOS file handle may be required in some special circumstances. The '''_get_osfhandle()''' function is provided in the '''fcntl.h''' header file to access DOS file handles.

			The following is an example program which demonstrates the feature.
			<syntaxhighlight>
			#include <proto/dos.h>
			#include <stdio.h>
			#include <fcntl.h>

			int main()
			{
			printf("0x%08x 0x%08x 0x%08x\n",
			(unsigned int)IDOS->Input(),
			(unsigned int)IDOS->Output(),
			(unsigned int)IDOS->ErrorOutput());

			printf("0x%08x 0x%08x 0x%08x\n",
			_get_osfhandle( fileno(stdin) ),
			_get_osfhandle( fileno(stdout) ),
			_get_osfhandle( fileno(stderr) ));

			return 0;
			}
			</syntaxhighlight>

			Note that this feature is available in newlib.library 53.20 and higher.

Steven Solie: /* Global Options */

2013-03-08T04:59:21Z

Global Options

← Older revision		Revision as of 04:59, 8 March 2013
Line 24:		Line 24:
	* IUtility		* IUtility

	=== ~~Global~~ Options ===		=== Options ===

	<syntaxhighlight>		<syntaxhighlight>

Steven Solie: /* Global Options */

2013-03-08T04:58:47Z

Global Options

← Older revision		Revision as of 04:58, 8 March 2013
Line 30:		Line 30:
	</syntaxhighlight>		</syntaxhighlight>

	Define '''__stdiowin''' to control the default standard I/O window which will open automatically if your program needs it. The default is "CON:64/48/800/200/[CLI command name\|Task name]".		Define '''__stdiowin''' to control the default standard I/O window which will open automatically if your program needs it. The default is "CON:64/48/800/200/[CLI command name\|Task name]/AUTO/CLOSE/WAIT".

	<syntaxhighlight>		<syntaxhighlight>

Steven Solie: /* Startup Code */

2013-03-08T04:58:22Z

Startup Code

← Older revision		Revision as of 04:58, 8 March 2013
Line 16:		Line 16:

	If '''argc''' is non-zero then it means the application was started from the Shell console and the normal C startup rules apply.		If '''argc''' is non-zero then it means the application was started from the Shell console and the normal C startup rules apply.

			=== Standard Interfaces ===

			The following interfaces are handled by the C startup code and are guaranteed to be present when main() is called:
			* IExec
			* IDOS
			* IUtility

			=== Global Options ===

			<syntaxhighlight>
			extern const char *__stdiowin;
			</syntaxhighlight>

			Define '''__stdiowin''' to control the default standard I/O window which will open automatically if your program needs it. The default is "CON:64/48/800/200/[CLI command name\|Task name]".

			<syntaxhighlight>
			extern int __unix_path_semantics;
			</syntaxhighlight>
			Define to 1 to enable POSIX style path semantics which is useful when porting applications from UNIX.