From c4d44dc55a1c93d47a86c8dff58487018ec663d9 Mon Sep 17 00:00:00 2001 From: cuz Date: Thu, 10 Oct 2002 21:45:44 +0000 Subject: [PATCH] Remove statement about initialization of locals git-svn-id: svn://svn.cc65.org/cc65/trunk@1461 b7a2c559-68d2-44c3-8de9-860c34a00d81 --- doc/cc65.sgml | 57 ++++++++++++++++++++++++--------------------------- 1 file changed, 27 insertions(+), 30 deletions(-) diff --git a/doc/cc65.sgml b/doc/cc65.sgml index 007fa6b1b..48b6fcc8d 100644 --- a/doc/cc65.sgml +++ b/doc/cc65.sgml @@ -327,42 +327,39 @@ and the one defined by the ISO standard: The compiler allows single line comments that start with //. This - feature is disabled in strict ANSI mode. -

+ feature is disabled in strict ANSI mode. +

The compiler allows unnamed parameters in parameter lists. The - compiler will not issue warnings about unused parameters that don't - have a name. This feature is disabled in strict ANSI mode. -

+ compiler will not issue warnings about unused parameters that don't + have a name. This feature is disabled in strict ANSI mode. +

The compiler has some additional keywords: -

- - -

- The keywords without the underlines are disabled in strict ANSI mode. -

+

+ + +

+ The keywords without the underlines are disabled in strict ANSI mode. +

The datatypes "float" and "double" are not available. -

+

The compiler does not support bit fields. -

- Initialization of local variables is only possible for scalar data - types (that is, not for arrays and structs). -

+

Because of the "wrong" order of the parameters on the stack, there is - an additional macro needed to access parameters in a variable - parameter list in a C function. -

+ an additional macro needed to access parameters in a variable + parameter list in a C function. +

Functions may not return structs (or unions), and structs may not be - passed as parameters by value. However, struct assignment *is* - possible. -

+ passed as parameters by value. However, struct assignment *is* + possible. +

Part of the C library is available only with fastcall calling conventions (see below). This means, that you may not mix pointers to those functions with pointers to user written functions. -- 2.39.5