ADVERTISEMENT

Tips & Tidbits

By Neil Ticktin, Editor-in-Chief

Tip of the month

Ira Ruben has written a useful code disassembler for ResEdit. However, it has drawbacks - in particular, it’s not very intelligent about handling data interspersed with the code (such as embedded string literals). Also, you can’t invoke it on just any resource type: if you come across a new type of code-containing resource (such as those “AINI” resources that System 7 uses), you have to modify ResEdit to be able to disassemble the new resource type.

MacsBug has much nicer disassembly facilities, and you can dump out different bits of memory using different formats if you choose. Wouldn’t it be nice if you could use these facilities on resources you were examining with ResEdit? Well, you can!

First of all, open the resource you want to examine with ResEdit. Make sure the resource is open for editing in a window (using any available editor - even the hex editor). Now, hold down the mouse button over ResEdit’s menu bar (an unused portion is best), and with your other hand, hit the interrupt button (or keyboard interrupt sequence) to get into MacsBug. Once you’re in MacsBug, you can let go of the mouse button.

Check the CurApName on the left of MacsBug’s display, to make sure you’re in ResEdit (it will be in the middle of calling MenuSelect). Now type

hd AINI

(replace “AINI” with whatever the type of the resource is that you want to examine). You will get a list of all resources of that type in the current heap zone, along with their starting addresses, lengths, resource IDs and names, and the refnum of the file they come from. Look for the one with the right ID or name. If you want to make sure you’ve got the right one, you can also use the command

file <refnum>

(replacing “<refnum>” with whatever the file refnum is for that resource) to make sure that the resource comes from the right file. Now you’re free to use commands like il and dm to examine bits of that resource.

If you’re making patches to code, you can use MacsBug’s dh command to check that you’ve got the right instruction words before making the modifications. Also, if you make any changes to a resource in ResEdit’s hex editor, you can go into MacsBug and disassemble that resource, and examine the effects of your changes immediately, before you save them.

- Lawrence D’Oliveiro

MPW as a “Real” Language

I though that I would write in on “How MPW scripts can perform tasks that might otherwise require you to code in a "real" computer language”. In the past few years, I've had to answer many users' questions on MPW, and I've accumulated a supply of interesting scripts and techniques. As an example, I could have answered Mike Scanlin's March Programmers' Challenge (count unique words) with this script:

Evaluate 
`Begin ; 
  Catenate 
  `GetFilename -t TEXT -b Count -m "UNIQUE WORD COUNT"` ; 
  Echo ; 
 End | 
Translate "A-Z ,." a-zn | 
Sort -unique | 
Count -l` - 1

Obviously, this entry doesn’t qualify because it is not in C, but it is yet another demonstration of MPW's power.

- Lee D. Rimar, Absoft

Source and Line info

After reading the tip of the month in the May issue, I thought others might like to see what I use for debug formatting. It has the same benefits as the DebugFStr routine (i.e., formatted output), but adds automatic source file and line number information to the debug output. Using the routine is identical to using printf, except it is now called dprintf. The dprintf routine itself is actually a macro that invokes one routine to store the caller's file name and line number, then calls the actual output routine.

To use dprintf, include dprintf.h in any files that use it, and make sure you've added ANSI or ANSI-small to your project. Call it anywhere just like you'd call printf.

/*-------- dprintf.h ---------*/

#define dprintf  dprintf_setup(__FILE__,__LINE__), dprintf_output

extern int dprintf_setup(const char *file, int line);
extern int dprintf_output(const char *fmt, ...);

/*-------- dprintf.c ---------*/

#include <stdarg.h>
#include <stdio.h>
#include "dprintf.h"

static int d_line;
static char d_file[32];

int
dprintf_setup(const char *file, int line)
{
 d_line = line;
 strncpy(d_file, file, sizeof(d_file));
 d_file[sizeof(d_file)-1] = 0;
 return 0;
}

int
dprintf_output(const char *fmt, ...)
{
 va_list ap;
 Str255 buf;
 
 sprintf(buf, "%s %d: ", d_file, d_line);
 va_start(ap, fmt);
 vsprintf(buf + strlen(buf), fmt, ap);
 va_end(ap);
 CtoPstr(buf);
 DebugStr(buf);
 return 0;
}

- Mark Nagel

System 7 FindFolder

There is a neat little function in System 7 called FindFolder(). It lets you find important system folders with little effort. I used it to find the preferences folder into which I placed my own folder. This worked fine under MacOS. I had a nice little combination of FindFolder(), FSOpen() and Create() calls. The problem begins with the A/UX way of seeing directories. These are more like Unix than Apple folders.

A/UX preferences folder = /mac/sys/System Folder/Preferences
Mac preferences folder = System Folder:Preferences

The A/UX path as presented is what FindFolder() returns. Unfortunately this does not work as a path for older Mac function calls. All the PB, PBH and other pre-System 7 calls do not understand this. to use this format directly you need to do either a) or b):

a) Use the FSSpec type of calls everywhere, which works very well after you get used to them; or b) Convert all your paths to the following:

A/UX FindFolder() gives:

/mac/sys/System Folder/Preferences

You need:

/:mac:sys:System Folder:Preferences

The key here being the '/:' at the beginning.

- CHUS-FAMUS

[Remember to keep them cards and letters coming. The more entries, the better the entries. - Ed.]