BOster
Legendary Poster
We are still on a 32bit Tools Release but trying to plan ahead for when we do move to 64bit.
When I check in a C BSFN it places the .h and .c files in \include and \source. It also "scrubs" the code and coverts to JDE 64bit compatible code and places in \include64 and \source64. It changes things like sizeof to jdesizeof , etc. Well, it also changes types so it converts things like "ULONG" and "unsigned long" to "unsigned int". For the majority of our code base that probably won't matter. However, we do have some BSFNs that load 3rd party DLLs, dynamically link to functions, etc. and in those cases variables, function pointer typedefs, etc. I need ULONG to be ULONG not "unsigned int".
Is there a way to prevent the JDE source code scrubber (shredder) from scrubbing sections of code or entire BSFNs? After we convert to 64bit will it still scrub code as its checked in or will I be able to declare a variable as ULONG and have it stay ULONG?
When I check in a C BSFN it places the .h and .c files in \include and \source. It also "scrubs" the code and coverts to JDE 64bit compatible code and places in \include64 and \source64. It changes things like sizeof to jdesizeof , etc. Well, it also changes types so it converts things like "ULONG" and "unsigned long" to "unsigned int". For the majority of our code base that probably won't matter. However, we do have some BSFNs that load 3rd party DLLs, dynamically link to functions, etc. and in those cases variables, function pointer typedefs, etc. I need ULONG to be ULONG not "unsigned int".
Is there a way to prevent the JDE source code scrubber (shredder) from scrubbing sections of code or entire BSFNs? After we convert to 64bit will it still scrub code as its checked in or will I be able to declare a variable as ULONG and have it stay ULONG?
