comparison doc/manual.docbook.sgml @ 240:b43e3e23583c

Added not about likely incompatibilities with source code from other assemblers when using the OS9 module target
author lost
date Sun, 16 Aug 2009 00:25:55 +0000
parents dca5938a64aa
children 6e2d03188d24
comparison
equal deleted inserted replaced
239:1106ec189e4f 240:b43e3e23583c
107 LWASM does NOT provide an OS9Defs file. You must provide your own. Also note 107 LWASM does NOT provide an OS9Defs file. You must provide your own. Also note
108 that the common practice of using "ifp1" around the inclusion of the OS9Defs 108 that the common practice of using "ifp1" around the inclusion of the OS9Defs
109 file is discouraged as it is pointless and can lead to unintentional 109 file is discouraged as it is pointless and can lead to unintentional
110 problems and phasing errors. Because LWASM reads each file exactly once, 110 problems and phasing errors. Because LWASM reads each file exactly once,
111 there is no benefit to restricting the inclusion to the first assembly pass. 111 there is no benefit to restricting the inclusion to the first assembly pass.
112
113 </para>
114
115 <para>
116
117 It is also critical to understand that unlike many OS9 assemblers, LWASM
118 does NOT maintain a separate data address counter. Thus, you must define
119 all your data offsets and so on outside of the mod/emod segment. It is,
120 therefore, likely that source code targeted at other assemblers will require
121 edits to build correctly.
112 122
113 </para> 123 </para>
114 124
115 <para> 125 <para>
116 126