Q35258: Why Compiling after Editing in M Shows Old Errors

Article: Q35258
Product(s): See article
Version(s): 1.00   | 1.00
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | | mspl13_basic
Last Modified: 20-OCT-1988

When using the M editor (either M.EXE or MEP.EXE) to correct compiler
or assembler errors, and then compiling/assembling from within M using
the COMPILE function, it is possible to get the old set of errors
returned. If the errors occur, check that the autosave switch is set
correctly. If autosave is off, the corrections are not saved before
compilation.

When turned on, the autosave boolean initialization switch causes the
current file to be saved whenever it is switched away from. The
default value is on, i.e., the files are automatically saved. The
setting can be changed from within the editor using Arg textarg Assign
or else in TOOLS.INI.

In either case, specify noautosave: to prevent automatic saving of
files, or autosave: to restore automatic file saving.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.