The real question is why didn't the author just put all the executable code in the resource fork.
Because the Mac OS X implementation of CFM doesn't support code fragments in resources. Believe me, I tried. (More implementation critiques, anyone?;))
Now, some of the most interesting google results so far are these: "MP3Virus.Gen alert during start-up" and "IDCS won't open - AWS plug in missing??". If Intego's virus scanner starts to generate lots of false positives for InDesign plugins, they've really shot themselves in their corporate foot.
Slashdot Mirror
Quoth plj: This only caused the I/O of some geeks to choke up due to wrong endianness.
You mean you missed the announcement about the new big-endian Pentiums?
Quoth Rosyna:
Because the Mac OS X implementation of CFM doesn't support code fragments in resources. Believe me, I tried. (More implementation critiques, anyone? ;))
Now, some of the most interesting google results so far are these: "MP3Virus.Gen alert during start-up" and "IDCS won't open - AWS plug in missing??". If Intego's virus scanner starts to generate lots of false positives for InDesign plugins, they've really shot themselves in their corporate foot.