6502/cc65
1
0
Fork 0
mirror of https://github.com/cc65/cc65.git synced 2025-02-05 20:31:53 +00:00
Code Issues Projects Releases Wiki Activity

Small improvement

Browse Source 
git-svn-id: svn://svn.cc65.org/cc65/trunk@3323 b7a2c559-68d2-44c3-8de9-860c34a00d81
This commit is contained in:
cuz 2004-12-02 22:26:17 +00:00
parent 4f66f980b2
commit 48a7d56619
1 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/cc65.sgml
View File

@ -437,7 +437,7 @@ and the one defined by the ISO standard:
conventions (see below). This means, that you may not mix pointers to conventions (see below). This means, that you may not mix pointers to
those functions with pointers to user written functions. those functions with pointers to user written functions.
<p> <p>
</itemize> </itemize>
There may be some more minor differences, I'm currently not aware off. The There may be some more minor differences, I'm currently not aware off. The
biggest problem is the missing float data type. With this limitation in biggest problem is the missing float data type. With this limitation in
@ -552,9 +552,9 @@ This cc65 version has some extensions to the ISO C standard.
<p> <p>
<item> cc65 implements flexible array struct members as defined in the C99 ISO <item> cc65 implements flexible array struct members as defined in the C99 ISO
standard. As an extension, these fields may be initialized. There are standard. As an extension, these fields may be initialized. There are
several exceptions, however (which is probably the reason why the several exceptions, however (which is probably the reason why the
standard does not define this feature, because it is highly standard does not define this feature, because it is highly
unorthogonal). Flexible array members cannot be initialized... unorthogonal). Flexible array members cannot be initialized...
<itemize> <itemize>
@ -652,7 +652,7 @@ The compiler defines several macros at startup:
<tag><tt>__CC65_STD__</tt></tag> <tag><tt>__CC65_STD__</tt></tag>
This macro is defined to one of the following depending on the <tt><ref This macro is defined to one of the following depending on the <tt><ref
id="option--standard" name="--standard"></tt> command line option: id="option--standard" name="--standard"></tt> command line option:
<itemize> <itemize>
<item><tt/__CC65_STD_C89__/ <item><tt/__CC65_STD_C89__/
@ -1037,14 +1037,20 @@ variables or functions into your asm statements. Code like this
<tscreen><verb> <tscreen><verb>
int foo; int foo;
int bar () { return 1; } int bar () { return 1; }
__asm__ ("lda _foo"); /* DON'T DO THAT! */ __asm__ ("lda _foo"); /* DON'T DO THAT! */
... ...
__asm__ ("jsr _bar"); /* DON'T DO THAT EITHER! */ __asm__ ("jsr _bar"); /* DON'T DO THAT EITHER! */
</verb></tscreen> </verb></tscreen>
<p> <p>
may stop working if the way, the compiler generates these names is changed in may stop working if the way, the compiler generates these names is changed in
a future version. Instead use the format specifiers from the table above. a future version. Instead use the format specifiers from the table above:
<tscreen><verb>
__asm__ ("lda %v", foo); /* OK */
...
__asm__ ("jsr %v", bar); /* OK */
</verb></tscreen>
<p> <p>