[EMAIL PROTECTED] wrote: > Yes it's a possible way of 'remembering' some values but we > ruled it out for the same reason as unnamed common - sooner > or later you'll interact with a subroutine or function that also > uses them and then ... > > btw named common isn't quite safe either - > it's possible that another routine uses the same name > for it's common ...
I hit that using &Pace at a previous job ... It stored file variables in named common, autogenerating the common name from the file name. Guess what - we had a name collision - and it was quite a subtle bug! I'd dug into the generated code before (surprise surprise) so as soon as I was shown the problem I guessed what it was. But the poor lass who first hit it was completely puzzled by it. > > What's really needed is a 'local static' modifier. Would be nice :-) Cheers, Wol ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
