T.R | Title | User | Personal Name | Date | Lines |
---|
148.1 | See 134.4 | TOOK::GUERTIN | Wherever you go, there you are. | Fri Jun 08 1990 14:14 | 0 |
148.2 | Global data must be readonly... | SMAUG::BELANGER | Quality is not a mistake! | Fri Jun 08 1990 14:52 | 9 |
|
This error results from the memory protection given to a global
variable. The only way to avoid this error is to define the global
data as either readonly or globaldef. Unfortunately, using either of
these causes the compile to flag the data as being not portable. In
order to make this code portable, you have to do some conditional
compilation.
~Jon.
|
148.3 | Making them static noshare did not solve it | BYBLOS::TAMER | | Fri Jun 08 1990 15:03 | 9 |
| Matt,
I had with my IPC code a couple of variables defined as static. Making them
static noshare or even taking out static all together did not solve it. I still
get the same problem and error messages at enrollment. The next reply will
include my *.map file
Regards,
Phil
|
148.4 | Global Variables were the Cultprits. Problem solved. Many thanks for .1 and .2 | BYBLOS::TAMER | | Fri Jun 08 1990 16:01 | 0 |
148.5 | IPC allowed in a MM ? | TENERE::DUNON | Paul Dunon - Telecom Engineering - VBO | Tue Jun 12 1990 06:36 | 11 |
|
In note 36.* I've been told that IPC should not be used in an access module,
because of its AST operations. Has that changed since January ??
Or does the SYS$QIOW revectoring mechanism of MCC allow the use of IPC ??
I would like to know the official up-to-date position of MCC engineering about
the use of IPC.
Thanks in advance,
-- Paul
|