From: uz Date: Sat, 29 Aug 2009 21:32:14 +0000 (+0000) Subject: Rewrote the paragraph about compiler limits and standard compliance. X-Git-Tag: V2.13.0rc1~176 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=7f7dc6929037a309533062c0ecb70f48a88bcea0;p=cc65 Rewrote the paragraph about compiler limits and standard compliance. git-svn-id: svn://svn.cc65.org/cc65/trunk@4080 b7a2c559-68d2-44c3-8de9-860c34a00d81 --- diff --git a/doc/cc65.sgml b/doc/cc65.sgml index dd2b10b33..165ae3534 100644 --- a/doc/cc65.sgml +++ b/doc/cc65.sgml @@ -403,37 +403,19 @@ search path for include files on startup. Differences to the ISO standard

+Apart from the things listed below, the compiler does support additional +keywords, has several functions in the standard headers with names outside the +reserved namespace and a few syntax extensions. All these can be disabled with +the command line +option. Its use for maximum standards compatibility is advised. + Here is a list of differences between the language, the compiler accepts, and the one defined by the ISO standard: - 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 can be disabled with the command line option. -

- The compiler has some additional keywords: -

- - -

- The keywords without the underlines can be disabled with the - command line - option. -

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

- The compiler does not support bit fields. -

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