A .r question

D

dlangschied

Member
I have programs that I am compiling in two environments, development and test. The propath is pretty much the same, with the execption of the path to the latest changes to the code (we use roundtable and have a workspace path that keeps track of the different development levels). The databases that are connected are the same. We noticed just recently that code that is identical in each environment has a different byte-size for the .r code. I have looked over every aspect of this very carefully and the .r code should be the same! I checked all the code and the story is the same. The difference in the byte-size is very small.

What is included in .r code? PROPATH info? XREF info? I really need to get to the bottom of this and have had zero success.
 
If I recall, there are various other bits in there like a date time stamp. Matching byte count is the wrong way to solve the problem of proving that they are identical.
 
Apart from anything else, the most obvious cause for something like this is 'Minimise r code size' being ticked/unticked in the two different compile sessons.
 
dlangschied said:
What is included in .r code? PROPATH info? XREF info? I really need to get to the bottom of this and have had zero success.
Click to expand...

Relative path info is stored in the debugger segment - this can be different.

Source:

Knowledgebase 16553 said:
Progress stores the names of all the sources that comprise the .r file
in the debug segment of the r-code so that if you're debugging, the
debugger can generate a debug listing file on the fly (if one doesn't
exist). This means that if you are compiling the same code from
different directories, the size of the r-code will be different
because the relative path name will be included. If I am in the test
directory and compile a procedure in that directory, it will be one
size. If I am in the test directory and compile the same piece of
code but it is in test/sub, the r-code will be bigger because the
relative path name will be included.
Click to expand...

I don't know if code can be compiled without the debugger segment.
 
Thanks to all of you for your speedy answers! I felt that something was there that caused the two .rs to be different, but I could not put my finger on it.
There is a slight change in the paths here by a few characters and, since there are only a few bits difference, this must be the reason. Again, thanks!
 
i want check, i assumed is right, if not correct me.

.r wil contain
1) encoding of source code
2) relative path of the file
3) but not xref related info


so when debugger is running
form .r it will create a debug file and go head right


plz add point if u want to share some thing. iam very much intrested to know wht is happening,iam learner i want to know .r contains and wht will debug look for, where xref come into point.
 
If your propath differs your r-code size may differ. /app/test and /app/devel are different sizes, if you are in a unix environment you can use the "strings" command to view the r-code
 
Maybe you have an include of a file that has two different versions in the two environements. So the final compiled code has different size.
Hoping to have been helpful.
 
You must log in or register to reply here.
Back
Top