MPW Commands Release Notes

Compare v3.6d1  [updated 7/22/02]

• Fixed crash caused by using the -h option without a following numeric argument.
• Added -i option, to skip the filetype check.

CreateMake v4.7.1d1  [updated 7/17/01]

• Added CarbonStdCLib.o to the list of Carbon libraries.
  Note - If CreateMake v4.7.1d1 (or later) is used to build a Carbon application or library, CarbonStdCLib.o must be installed in the {PPCLibraries} directory.

DirectoryMenu v3.5.1d1  [updated 8/21/01]

• Added the ability to create separator lines in the menu by specifying directories whose names begin with "(-".

DumpPEF v2.3.2d2  [updated 5/30/01]

• DumpPEF now has the ability to create MPW Shell markers for routines within the code section. The markers are created when disassembling the code section if traceback tables containing the routine names are present, the -markcode option has been specified, and the -ntb option has NOT been specified. The routine names are unmangled if -u has been specified.
• Added a new command line option: -markcode
• Bug fix - The commando dialog had a typo in the option for dumping the traceback section. It was generating "do -b" instead of "-do b".

Make v4.1.2d1  [updated 9/10/01]

• Bug fix - Make would get confused if a build rule was immediately followed by a !include line.

MakeSYM v2.0.1d1  [updated 8/27/01]

• Bug fix - The command line options were order sensitive.
• Bug fix - The -only filenames were case sensitive.
• Bug fix - The usage messages were incorrect.

ModPEF v1.0.2d2  [updated 4/26/01]

• Bug fix - ModPEF v1.0.2d1 would report an internal error if it tried to read a PEF section with a length of 0.

PPCAsm v1.4b2  [updated 4/12/01]

• PPCAsm now really supports files with unix line termination conventions.
• PPCAsm now enforces the positioning of the FUNCTION directive more accurately. The FUNCTION debugging directive is only allowed in a read-only CSect. Therefore, the MakeFunction macro supplied on page 3 of the PPCAsm v1.3 release notes must be modified slightly to be conformant. The positions of the final FUNCTION and CSECT directives should be reversed. Previously, the FUNCTION directive appeared within the DS section, which is not read-only.

Rez v3.5d1  [updated 4/25/01]

• Added support for macros with parameters. The syntax is -
  
  #define macroName([param1[,param2]...]) [value]
  
  The macro name must be immediately followed by the left parenthesis. Everything up to and including the right parenthesis must be on one line. If the macro definition spans more than one line, line continuation characters must be used. When the macro is invoked, whitespace may appear between the macro name and the left parenthesis, however, the left parenthesis must be on the same line as the macro name. The arguments may appear on multiple lines and the line continuation character is optional. A macro can have zero parameters. When such a macro is invoked, an empty argument list must be provided.
• Changed the way duplicate resource definitions are handled. Rez used to handle duplicate resource definitions differently depending on whether the -a option had been specified. If the -a option was not specified, a fatal error was reported if a duplicate resource definition was encountered. If the -a option was specified, no error or warning was reported and the last definition was the one that was used. Rez now always reports a warning if it encounters a duplicate resource definition and the duplicate definition is ignored.
• Bug fix - The word "occurred" was misspelled in two error messages.

RezDet v3.6d2  [updated 7/22/02]

• Added -useDF option, to allow the tool to examine resources stored in the data fork of a file (i.e. Mac OS X resource files)
• Removed warning about resource attributes bit 7 being set. This bit is now used for the resSysRef attribute.

SC/SCpp v8.9.0d3  [updated 11/22/00]

• This version of the SC compilers fixes some language recognition bugs. SC[pp] uses the same code base as MrC[pp] for its front end, i.e., language recognition phase. This version of SC[pp] conforms with version 5.0d3 of MrC[pp].
• Several bugs in which the compiler generates bad code have been fixed.

SC/SCpp v8.9.0d2  [updated 6/19/00]

• This version of the SC compilers fixes a number of language recognition bugs. SC[pp] uses the same code base as MrC[pp] for its front end, i.e., language recognition phase. This version of SC[pp] conforms with version 5.0d2 of MrC[pp].

SC/SCpp v8.9.0d1  [updated 3/3/00]

• This version of the SC compilers fixes a number of language recognition and code generation bugs. SC[pp] uses the same code base as MrC[pp] for its front end, i.e., language recognition phase. This version of SC[pp] conforms with version 5.0d1 of MrC[pp].
• Support for templates and namespaces has been greatly improved. Please see the MrC release notes for details.
• Bug fix - SC[pp] no longer calls operator delete when an exception is thrown during a call to the placement variant of operator new. Note that CPlusLib.o v4.2d1 (or later) is required for this fix.

SC/SCpp v8.8.4  [updated 12/13/99]

• The SC compilers have been promoted to "final" status.
• This version of the SC compilers fixes a number of language recognition bugs. SC[pp] uses the same code base as MrC[pp] for its front end, i.e., language recognition phase. This version of SC[pp] conforms with version 4.1 (final) of MrC[pp].
• Namespace recognition is enabled in this version of SCpp.

Search v3.6d1  [updated 7/23/02]

• Added -ext option. This option allows the user to filter the files to search based on filename extensions. Multiple extensions can be supplied by separating them with comma characters. For example:
  
  search -s /foo/ -rd -ext .c,.cpp,.h Volume:MySources:
  
  will perform a recursive search through the volume hierarchy at Volume:MySources:, searching all files whose filenames end with '.c', '.cpp', or '.h'.

SendAE v1.3.1d1  [updated 7/11/01]

• Bug fix - If the -dot option was specified, random characters were appended to the data when it was written to standard output.

SetVersion v3.5d3  [updated 5/30/01]

• Bug fix - If the -i option was specified with a resource ID > 2, the 'vers' resource that was created had the wrong contents.
• Bug fix - If -csource, -psource, or -rezsource was specified and the source file had been checked out read-only, SetVersion modified the file anyway. SetVersion now checks to see if the file has a 'ckid' resource. If so, and the file is read-only, a warning is reported and the file is not modified.
• Bug fix - Added a missing call to Release().

SetVersion v3.5d2  [updated 2/20/01]

• SetVersion now recognizes "final candidate" version number schemes, such as 1.0f2. This applies to both the -version option, as well as the -stage option. The -stage option now recognizes the new "final" specifier. When used, the short version string will be formatted properly, with the "f" build stage letter, and the specified build stage level number. Note that when a final candidate version resource is created, the BCD-encoded version number field of the 'vers' resource will always have a 0 stage level number, so that when the eventual "Golden Master" build occurs, it will not have a BCD-encoded version number less than any of the "final candidate" builds.

Sort v3.5.1d1  [updated 6/19/01]

• Bug fix - If the -quote option was specified, the output from Sort was not correct.

WhereIs v3.4.2  [updated 12/03/02]

• Bug fix - When run in the Classic environment of Mac OS X, with no -s option supplied, the tool would receive a working directory reference number from PBHGetVol, rather than a raw volume reference number. When passed to PBCatSearch, the wdRefNum was not recognized as a valid volume, and the function would return an error. The tool now immediately converts a returned wdRefNum into a valid vRefNum before using it anywhere else.