| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2572.1 | | TLE::REAGAN | All of this chaos makes perfect sense | Fri Dec 22 1995 09:52 | 9 |
| 2572.2 | still not working with T5.6 | UTOPIE::RANISCH | How many bits do you really need ? | Tue Jun 03 1997 08:55 | 8 |
| Johm,
I just ran this example against the 5.6 compiler on OpenVMS/Alpha 7.1
The problem still exists. the %PROC is generated by the compile and not
by the user. The workaround you mentioned is working, but not too nice.
thanx for your support
peter
|
| 2572.3 | | TLE::REAGAN | All of this chaos makes perfect sense | Tue Jun 03 1997 11:05 | 25 |
| Why did you think that T5.6 might have "fixed" anything. I re-read my
reply and I didn't say that it was a bug. The current behavior is
the intended behavior.
What would you like us to do? Our implementation of schema types
include generating routines and data structures to support schema
between modules. When using OpenVMS shareable images, the user
unfortunately has the responsibility to helping the compiler find
those routines and data structures inside the shareable image via
the symbol vector.
Do you want us to get rid of the %PROC (and other routines)? That
would be very hard to do.
Do you want the compiler to help you know about the %PROC (and other
routines) so that you could put them into your symbol_vector more
easily?
My suggestion of not putting schema types in modules that generate code
is one that I recommend. What does the customer find "not too nice"
about it? Seperating the interface (including the schema type
definition) from the implementation (which is the shareable image)
is a good thing to do in general.
-John
|