Commodore PC - Page 268

196 MS-DOS User's Reference
Example: w*
This example causes the line-number information in the object file
filaobj to be copied to the map file file, map: i )
link f i le/1 i nenumbers , , ern+5 1 ibf p
Preserving Lowercase W
Syntax:
The/noignorecase /noignorecase ^J
°P"on The /noignorecase option directs link to treat uppercase and
lowercase letters in symbol names as distinct letters. Normally, , j
link considers uppercase and lowercase letters to be identical, ^—'
treating the words "TWO", "two", and "Two" as the same symbol.
When you use the /noignorecase option, however, the linker
treats "TWO", "two", and "Two" as different symbols. (vs_^
Typically, you use the /noignorecase option with object files
created by high-level-language compilers. Some compilers treat
uppercase and lowercase letters as distinct letters and assume the \^J
linker does the same.
If you are linking modules created with masm to modules created
with a case-sensitive language such as C, make sure public sym- \^J
bols have the same sensitivity in both modules. For example, you
could make all variables in C distinctive by spelling, regardless of
case, and then link without the /noignorecase option. Another ^J
alternative would be to use the /ML or MX option to make public
variables in masm case-sensitive. Then link with the
/noignorecase option. i j
Minimum abbreviation: /noi
Example: < j
The following command causes the linker to treat uppercase and
lowercase letters in symbol names as distinct letters. The object
file file, obj is linked with routines from the standard C language I )
library \Slibclib located in the \lib directory. The C language ^^
expects uppercase and lowercase letters to be treated distinctly:
link file1+file2/noi77,em+mlibfp ^^J