Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!tut.cis.ohio-state.edu!rutgers!att!pegasus!ech
From: ech@pegasus.ATT.COM (Edward C Horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: XFCN/XCMD string in LSC C v3.0
Message-ID: <2784@pegasus.ATT.COM>
Date: 13 Apr 89 21:42:02 GMT
References: <6944@hoptoad.uucp>
Organization: AT&T ISL Middletown NJ USA
Lines: 20

From article <6944@hoptoad.uucp>, by tim@hoptoad.uucp (Tim Maroney):

> One more note.  This whole thing got started because of a discussion of
> string constants.  Uh, guys, you're not supposed to be using those on
> the Mac, ya know.  Sure it would be nice if every compiler let you put
> them in code space, but for internationalization, you're supposed to
> put all of them into 'STR ' and 'STR#' resources.  I have not found
> this to be a real burden as long as you run MultiFinder; you can use
> ResEdit while your development system stays up.

If all you develop are applications, which own all resource IDs from
128 through 2^15-1, or DRVRs (each which owns 32 IDs of every conceivable
resource) or one of the other "blessed" code types, this is a reasonable
approach.  What STR and STR# resource IDs should an XCMD use?  Or should
I use GetNamedResource and HOPE nobody else uses a STR# named "godzilla"?

I'm not challenging the value of Tim's approach where it's cleanly
applicable, but what to do where it isn't?  DTS?

=Ned Horvath=