Extpgm() or Extproc()?

Since the list is so quiet, I might as well drop an item in that I've been thinking around for a day or so.

While looking through a bunch of code to locate where a problem might be found, I noticed that an outer ILE CL module contained a CALLPRC XYZRPG for an RPG procedure. As I was going through the RPG code, I also noticed that, as a module, it was actually structured and apparently intended to be a whole program object.

That is, the PR-spec had EXTPGM( XYZRPG ) rather than being a *NOMAIN module with EXTPROC( XYZRPG ).

It's not so much that I think that's wrong, in a compile/bind sense. It all apparently compiled and was bound exactly as the developer told it to be (regardless of intent). It's more that the "mechanism" isn't clear. I'm not sure that it would have ever crossed my mind even to try to do things that way.

Is there anybody out there who might be willing to illuminate potential unexpected side-effects of this structure?

Tom Liotta