Dual Support PB604 and PB610 Identification

[dfw1417]

I have a program developed originally on the 32 bit versions currently working well and also same source compiles and runs well on 6.10 version. I have placed the 32 bit version in PBUNI604 folder and the 64 bit version in PBUNI610 folder. The program is a project and is setup so that no compiler info is saved or stored once compiled in the project. I want to continue developing these as 32 and 64 bit versions as clones of each other. What I want to do now is find a way to adjust an added string content to reflect whether the program when running is the 32 bit version or the 64 bit version and I would like to do it dynamically. In other words I dont want to manually assign "32" to the string and "64" to the same string based upon which version I am running because then the source codes for each project would not be the same. I want a way using the same source code to be able to identify and adjust programatically when run the string contents to either "32" or "64" to reflect which version 32 or 64 is running. Something similar to the CompileIf but just identifying 32 or 64 bit version. I was thinking along the lines of code which throws an error in the 64 bit version but not in the 32 bit version when the program starts up which then adjusts the string contents based on the On Error Syntax. Is there an easy way to do this? My main objective is that the source code in the project must remain the exact same for both 32 and 64 bit versions to make support and development fluid and easy. Thanks in advance for any thoughts.

[jacdelad]

Hi,
if I understand your request right, you can use the system constant #PB_Processor_x64:

Code: Select all

CompilerSelect #PB_Compiler_Processor
  CompilerCase #PB_Processor_x64
    #MyConst$ = "x64"
  CompilerCase #PB_Processor_x86
    #MyConst$ = "x86"
  CompilerCase #PB_Processor_Arm32
    #MyConst$ = "ARM32"
  CompilerCase #PB_Processor_Arm64
    #MyConst$ = "ARM64"
  CompilerDefault
    #MyConst$ = "Uh, oh..."
CompilerEndSelect
Debug #MyConst$

[mk-soft]

Code: Select all

CompilerSelect #PB_Compiler_Processor
  CompilerCase #PB_Processor_x86
    #RTProcessor = "x86"
  CompilerCase #PB_Processor_x64
    #RTProcessor = "x64"
  CompilerCase #PB_Processor_Arm32
    #RTProcessor = "arm32"
  CompilerCase #PB_Processor_Arm64
    #RTProcessor = "arm64"
CompilerEndSelect

Debug #RTProcessor

[Michael Vogel]

Brute short version...

Code: Select all

a=(#PB_Compiler_Processor-1)/2
Debug Mid("ARMX",(~a&2)<<1,3) + Str(32<<Bool(a%3))

[Kiffi]

Brute short version...

Code: Select all

a=(#PB_Compiler_Processor-1)/2
Debug Mid("ARMX",(~a&2)<<1,3) + Str(32<<Bool(a%3))

[Quin]

Brute short version...

Code: Select all

a=(#PB_Compiler_Processor-1)/2
Debug Mid("ARMX",(~a&2)<<1,3) + Str(32<<Bool(a%3))

Wow. I didn't think it was possible to code golf in PB like that . Good job!

[dfw1417]

Thanks All

[blueb]

Code: Select all

;Is 32/64Bit
If SizeOf(Integer) = 8
     Debug "64-bit system (x64)"
ElseIf SizeOf(Integer) = 4
     Debug "32-bit system (x86)"
Else 
     Debug "Something wrong here."
EndIf

[Fred]

#PB_Compiler_64Bit can be used for this:

Code: Select all

Debug #PB_Compiler_64Bit

[Blue]

Brute short version...

Code: Select all

a=(#PB_Compiler_Processor-1)/2
Debug Mid("ARMX",(~a&2)<<1,3) + Str(32<<Bool(a%3))

I’m in awe… but

#PB_Compiler_64Bit can be used for this:

Code: Select all

Debug #PB_Compiler_64Bit

So simple and, especially, so much clearer.

[Quin]

Brute short version...

Code: Select all

a=(#PB_Compiler_Processor-1)/2
Debug Mid("ARMX",(~a&2)<<1,3) + Str(32<<Bool(a%3))

I’m in awe… but

#PB_Compiler_64Bit can be used for this:

Code: Select all

Debug #PB_Compiler_64Bit

So simple and, especially, so much clearer.

True, unless you want to tell more than just 32 or 64-bit. Michael's method can also tell you ARM/ARM64

[Michael Vogel]

Endless variations are possible...

Code: Select all

CompilerIf #PB_Compiler_Version<600
	Debug Mid("ARMX",Bool(#PB_Compiler_Processor&6-6)<<2,3) + Str(32<<Bool(#PB_Compiler_Processor&$D=4))
CompilerElse
	Debug Mid("ARMX",Bool(#PB_Compiler_Processor&6-6)<<2,3) + Str(32<<#PB_Compiler_64Bit)
CompilerEndIf

[Blue]

Endless variations are possible...
[…]

oh yes.
Endless obfuscations too.
But, as i commented above, I’m still in awe of the intellectual contorsions.
It takes a code acrobat to come up with something like this, and I’ve always envied acrobats.

[Jeromyal]

Endless variations are possible...
[…]

oh yes.
Endless obfuscations too.
But, as i commented above, I’m still in awe of the intellectual contorsions.
It takes a code acrobat to come up with something like this, and I’ve always envied acrobats.

Does being skilled at inserting a foot in own ones mouth count? There are days I could put on a great act.

Code: Select all

"Foot in one's mouth" is an idiom that means to say something foolish, embarrassing, or tactless. For example, "Jane put her foot in her mouth when she called him by her first husband's name". This idea is sometimes expressed as having "foot-in-mouth disease". "Foot-in-mouth disease" is an informal, facetious term for the habit of making inappropriate, insensitive, or imprudent statements.

[Blue]

[...]
Does being skilled at inserting a foot in own ones mouth count? There are days I could put on a great act.
[…]

Are you saying you're agile at putting your foot in your mouth ?
That would certainly count... however you do it.
We run a club for that. You could join.