Kbase 13558: r-code in V7, Segment limits and what they are
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
r-code in V7, Segment limits and what they are
This notebook entry deals with the difference between V6 and V7 r-code
and the different segments of r-code in version 7
The entire structure for r-code files was changed when the
product went from version 6 to version 7. It is now a segmented
architecture which provides a number of features.
The two primary ones are:
1) R-Code portability within same window systems
2) R-Code files can now be larger than 63k in size
In fact, the size of an r-code file in V7 is pretty much
unlimited. While there are some limits, if they are reached a
small restructuring of some of the procedure code file can get
by the problem. Below is a detailed listing of the r-code
segments and what their limits are:
- One or more text segments, each up to 60k bytes
- Up to 4 expression code segments, each up to 60k bytes
- One action code segment for each internal procedure and trigger
plus one action code segment for main procedure, up to 60k each
- One debugger segment up to 60k each
- One initial value segment up to 60k each
- One frame segment per frame in the r-code file, up to 32k each
Yes, r-code files will be bigger in V7. This is by design and will
not be changed. There is no cause for alarm however since even
though the r-code may grow in size, it will stil be usable by
Progress. (The only place that could possibly be cause for alarm is
if someone is distributing their application on a fixed size media and
it may now need more than the media can supply. This is simply a
side-effect that the vendor will have to deal with.)
Progress Software Technical Support Note # 13558