On Mon, Dec 15, 2014 at 3:17 PM, Gary Weinhold <[email protected]> wrote:
> I don't know just when LE decides it has to build an enclave, but if your > routine could be invoked by a non-LE routine (a transaction written in > assembler, for example), perhaps it would cause significant overhead. If > that's impossible, then no worries. Even it were possible, I don't know > how that overhead compares to storage obtain/release. A point to remember. But, in this case, the routine is going to be (supposedly) running as the main program in a started task. One possible problem _might_ be that the routine must run in AR mode to access a data space. So I'll likely need to read up on LE and AR mode. I'd almost be that LE was _not_ designed with AR mode routines in mind. So I'll likely need to be switching back and forth if I do much with LE. Hum, perhaps my love of using C run-time subroutines needs be rethought. Or maybe I could use the Metal C subroutines and so bypass LE. <sigh> Decisions! Decisions! Maybe I'll just go back to playing "Midnight Castle". It's easier. -- While a transcendent vocabulary is laudable, one must be eternally careful so that the calculated objective of communication does not become ensconced in obscurity. In other words, eschew obfuscation. Maranatha! <>< John McKown
