In message
<13e4ae055d203648a4121114f2458c8c7a4adb8...@tefnut.perth.itvision.com.au>
, Adrian Halid <[email protected]> writes
Thanks for the help.
It seems once you name your common block you do not get the error anymore.
I don't think that's the problem ...
Just having a read of the documentation about the common statement in
the documentation.
"A common area can be either named or unnamed. An unnamed common area is
lost when the program completes its execution and control returns to
the UniVerse
command level. A named common area remains available for as long as the user
remains in the UniVerse environment."
From what it says I should be able to have them unnamed and loose it
between subroutine calls.
That may well depend on your emulation. AIUI, unnamed common persists
for as long as a program runs. It's returning to TCL that clears unnamed
common (as I say, AIUI, I've never used unnamed common).
Named common persists until you log out. And I've had several obscure
bugs where something tries to changed the size of common - that's not
allowed.
So if subroutine A effectively contains "COMMON A,B,C" while subroutine
B effectively contains "COMMON A,B,C,D,E,F" then running them in the
same execution environment *will* cause a crash because B has tried to
redefine common.
Regards
Adrian Halid
Senior Analyst/Programmer
Cheers,
Wol
--
Anthony W. Youngman <[email protected]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
