According to its documention, [suspend] reports "Mac OS suspend/resume events. The behavior is emulated on Windows."
The thing is, Mac OS hasn't been sending suspend or resume events since Mac OS X was introduced. Those events were only in the Classic Mac OS. I've seen some discussion indicating that this sort of thing is considered a security issue under Unix. In addition, an application does't really notice the difference between being frontmost and non-frontmost app under preemptive multi-tasking, not the way it did under the Classic Mac OS cooperative multitasking model.
I'm not aware if there is even a way for an application to hack into this information under OS X (or, for that matter, any Unix OS).
Given the discussion here and my own (brief) tests, it seems that [suspend] just sits there doing nothing. Still, that's better than millions of existing patches breaking.
Nevertheless, it might be nice to have a note about what's (not) going on in the documentation. Gregory?
So it seems" Maybe it's still included in Max for backwards compatibility as it worked on an older OS?" was a correct assumption.
Does seem like [suspend] documentation needs a facelift.
For a Max user like me who would like Max to respond (ie by opening/closing a UI window) when it's brought to the front or sent back I guess Apple Script via [tap.applescript] might be useful, but not ideal. I appreciate the insight Pater brings to teh OS environment....