Symantec Top 10

By Craig Conner

This month we take a look at some new technologies, and then look at SPM. We also visit a few interesting topics from the newsgroups.

Q: I would like to do development of QuickDraw 3D applications using SPM, but I am getting “unrecognized pragma” warnings after patching the QD3D headers and samples.

A: The latest versions of the QuickDraw 3D headers (from the April ’96 SDK) do not need any changes; however, they do include a pragma option, !align_arrays, which is not supported (and not necessary) on a PPC machine. Since it is just a warning, you can safely ignore it.

Also, to compile and debug the sample projects, you will need to:

1. open and update the project files;

2. enable Exception Handling in the PowerPC translator;

3. enable Background Events; and

4. replace the .xcoff libraries with their non-.xcoff versions using the Script menu item Replace.xcoff libs.

Q: Now that SPM supports 68K, can I create 68K code resources?

A: Yes. You will need to specify the correct link options via the Link Options, and you will need to specify the resource type and ID in the Command Line Linker Options page in the Additional Command Line Options.edit pane with -rt type=ID. Also, the SPM adds a 'SIZE' resource to your target, which can be removed with ResEdit. Contact Symantec Technical Support for a project model to ease set-up.

Q: Can I use SPM to build Apple Shared Library Manager libraries?

A: Yes. There is a project model for building shared libraries on our ftp site at ftp://ftp.symantec.com.

Q: I would like to be able to write 68K assembly code, but the 8.1 C translator does not allow that. Is there a way to use 68K assembly code in SPM?

A: Yes. In the Goodies:Tech Support Goodies folder are 68K Assembly and 68K Pascal translators. These two translators allow you to compile 68K code via ToolServer, but provide a consistent user interface within the Symantec Project Manager. These two translators also support the new ability of SPM to combine 68K and PPC source and libraries within the same project, to create a fat application using a single project file.

Q: I want to use MrC++ to build a VA application, but if I specify MrC and MrC++ as the translators, I get a bunch of undefined Bedrock symbols.

A: MrC and MrC++ do not currently support the native exception handling of the Symantec C and C++ translators, but by replacing BRLib.o and PPCCPlusLib TCL.o with BrLib (non-native eh).o and PPCCPlusLib TCL_BRLibeh.o [I suspect he means PPCCPlusLib TCL_BELeh.o here - man], you can use MrC and MrC++ to generate your VA application.

Q: I am getting this link error when building an application in the SPM:

 "Toolserver 's must occur in pairs."

What causes it?

A: Most likely, you have a single-quote character in a folder located in the path to your project folder, something like Dave's Folder. ToolServer makes special use of single-quote characters in pathnames. Removing the apostrophe will fix the problem but make your filenames sound ungrammatical. So much for good English.

Q: When trying to create a PCI driver, I get these link errors:

Multiply Defined Symbol:

BlockMove (DriverServicesLib, InterfaceLib)

Multiply DefinedSymbol:

BlockMoveData (DriverServicesLib, InterfaceLib)

The libraries involved are:

DriverServicesLib 1.0.2 from the April 96 SDK 2 disk

InterfaceLib 1.1 from our Release 5 CD

How do I avoid this?

A: This is a bug in the DriverServicesLib. These symbols should not have been redefined in this library. Hopefully, by the time you read this Apple will have released a newer version.

Q: And now a Java question. When compiling my Java project I am getting the compile error:

Error: File Foo.class does not contain Foo as expected, but java.somepackage.Foo. Please remove the file.

What gives?

A: The project is looking for something in the java.somepackage.Foo package, but can not find it. Most likely you forgot to import it. Add an import java.somepackage.Foo line and it should fix it.

Q: Is there a TCL archive somewhere?

A: You can now find indices at:

http://rhino.harvard.edu/dan/TCLArchive.html

and the files themselves at:

ftp://rhino.harvard.edu/pub/dan/TCL/

If you have classes you want to add, upload them to:

ftp://rhino.harvard.edu/incoming/

and send Dan Crevier at dan@rhino.harvard.edu a message about it. By the way, thanks, Dan.

Q: I am trying to port a PowerPlant application to Symantec C++, but I get the following error:

 File "PPobClasses.cp"; Line 57
 Error:   cannot implicitly convert
 from: LButton *(*"C++")(LStream *)
 to  : void *(*"C++")(LStream *)

on the line:

URegistrar::RegisterClass(LButton::class_ID,
 LButton::CreateButtonStream);

Why?

A: The second parameter of RegisterClass() is a ClassCreatorFunc, defined as:

typedef void* (*ClassCreatorFunc)(LStream *);

The problem is that each object’s creator function (as for LButton above) returns a pointer to a class, which violates contravariance rules of C++.

Thanks to multiple people here in tech support, who each individually probably wrote more for this article than I did.