This is as expected c seems to be treated as int while d seems to be float Still, int math is used (d=3.0 and not 3.3333). This is IMHO not as it should be as data type is explicitly declared, regardless whether c and d are assigned to a int and float math should be used e and f are treated as float and float math is used This is as expected So far, it seems type of variables is determined by the type of their initialization value. This makes DIM statement useless though (except for arrays) g and h are treated as integers and int math is used This is confusing to me, as I would expect h be float (as it is assigned to a float expression). It seems to be inconsistent with what happens above. This raises an issue: If I have an expression where only int variables are used, but I want that expression to be calculated using float math, how can I do it? In the example above I do want h to be 3.33333 This works for j but not for k It seems this gives me a “workaround” for j (which seems a bit inconsistent as it is initialized with an int, see c above) but this means I need to “duplicate” my variables at each calculation

 a=10
 b=a/3
 
 PRINT "a,b "; a,b
 
 DIM c,d AS FLOAT
 c=100
 d=c/3.0
 
 PRINT "c,d "; c,d
 
 e=10.0
 f=e/3.0
 
 PRINT "e,f "; e,f
 
 
 g=10
 h=g/3.0
 
 PRINT "g,h "; g,h
 
 
 i=10
 DIM j AS FLOAT: j=i
 j=j/3.0
 DIM k AS FLOAT: k=i/3.0
 
 PRINT "i,j,k "; i,j,k
 

• bug_data_type.bas

The instructions here refer to compiling the example from the command line. For Microsoft Windows users we suggest using UGBASIC-IDE, which allows you to compile the example with just one click.

In order to compile and run the example, you need to have the Altirra emulator, and in particular that the altirra executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.atari bug_data_type.bas -o example.xex
 altirra example.xex
 
 # Windows 
 ugbc.atari.exe bug_data_type.bas -o example.xex
 altirra example.xex

In order to compile and run the example, you need to have the Altirra emulator, and in particular that the altirra executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.atarixl bug_data_type.bas -o example.xex
 altirra example.xex
 
 # Windows 
 ugbc.atarixl.exe bug_data_type.bas -o example.xex
 altirra example.xex

In order to compile and run the example, you need to have the VICE emulator, and in particular that the x64sc executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.c64 bug_data_type.bas -o example.prg
 x64sc example.prg
 
 # Windows 
 ugbc.c64.exe bug_data_type.bas -o example.prg
 x64sc example.prg

In order to compile and run the example, you need to have the VICE emulator, and in particular that the x64sc executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.c64reu bug_data_type.bas -o example.prg
 x64sc -reu example.prg
 
 # Windows 
 ugbc.c64reu.exe bug_data_type.bas -o example.prg
 x64sc -reu example.prg

In order to run the example, you need to have the YAPE emulator. In particular that the yape executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.plus4 bug_data_type.bas -o example.prg
 yape example.prg
 
 # Windows 
 ugbc.plus4.exe bug_data_type.bas -o example.prg
 yape example.prg

In order to run the example, you need to have the VICE emulator. In particular that the xplus4 executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.plus4 bug_data_type.bas -o example.prg
 xplus4 example.prg
 
 # Windows 
 ugbc.plus4.exe bug_data_type.bas -o example.prg
 xplus4 example.prg

In order to compile and run the example, you need to have the XROAR emulator, and in particular that the xroar executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.d32 bug_data_type.bas -o example.bin
 xroar -rompath (your rom path) example.bin
 
 # Windows 
 ugbc.d32.exe bug_data_type.bas -o example.bin
 xroar.exe -rompath (your rom path) example.bin

In order to compile and run the example, you need to have the XROAR emulator, and in particular that the xroar executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.d64 bug_data_type.bas -o example.bin
 xroar -rompath (your rom path) example.bin
 
 # Windows 
 ugbc.d64.exe bug_data_type.bas -o example.bin
 xroar.exe -rompath (your rom path) example.bin

In order to compile and run the example, you need to have the DCMOTO emulator, and in particular that the dcmoto executable is accessible.

Then, type this command on the command line and on the emulator:

 # Linux 
 ugbc.pc128op bug_data_type.bas -o example.k7
 dcmoto
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC
 
 # Windows 
 ugbc.pc128op.exe bug_data_type.bas -o example.k7
 dcmoto
 (choose example.k7)
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC

In order to compile and run the example, you need to have the DCMOTO emulator, and in particular that the dcmoto executable is accessible.

Then, type this command on the command line and on the emulator:

 # Linux 
 ugbc.pc128op bug_data_type.bas -o example.k7
 dcmoto
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC
 
 # Windows 
 ugbc.pc128op.exe bug_data_type.bas -o example.k7
 dcmoto
 (choose example.k7)
 (choose BASIC 128)
 CLEAR,&H2FFF: LOADM"CASS:",R: EXEC

In order to compile and run the example, you need to have the VICE emulator, and in particular that the xvic executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.vic20 bug_data_type.bas -o example.prg
 xvic --memory 24k example.prg
 
 # Windows 
 ugbc.vic20.exe bug_data_type.bas -o example.prg
 xvic --memory 24k example.prg

In order to compile and run the example, you need to have the Speccy emulator, and in particular that the speccy executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.zx bug_data_type.bas -o example.tap
 Speccy example.tap
 
 # Windows 
 ugbc.zx.exe bug_data_type.bas -o example.tap
 Speccy example.tap

In order to compile and run the example, you need to have the openMsx or the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.msx1 bug_data_type.bas -o example.rom
 openmsx -cart example.rom
 
 # Windows 
 ugbc.msx1.exe bug_data_type.bas -o example.rom
 openmsx -cart example.rom

 # Linux 
 ugbc.msx1 bug_data_type.bas -o example.rom
 bluemsx example.rom
 
 # Windows 
 ugbc.msx1.exe bug_data_type.bas -o example.rom
 bluemsx example.rom

In order to compile and run the example, you need to have the openMsx or the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.coleco bug_data_type.bas -o example.rom
 openmsx -machine \"COL - ColecoVision\" -cart example.rom
 
 # Windows 
 ugbc.coleco.exe bug_data_type.bas -o example.rom
 bluemsx -machine \"COL - ColecoVision\" example.rom

 # Linux 
 ugbc.coleco bug_data_type.bas -o example.rom
 bluemsx /machine \"COL - ColecoVision\" /rom1 example.rom
 
 # Windows 
 ugbc.coleco.exe bug_data_type.bas -o example.rom
 bluemsx  /machine \"COL - ColecoVision\" /rom1 example.rom

In order to compile and run the example, you need to have the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.sc3000 bug_data_type.bas -o example.rom
 bluemsx /machine \"SEGA - SC-3000\" /rom1 example.rom
 
 # Windows 
 ugbc.sc3000.exe bug_data_type.bas -o example.rom
 bluemsx  /machine \"SEGA - SC-3000\" /rom1 example.rom

In order to compile and run the example, you need to have the BlueMSX emulator, and in particular that its executable is accessible.

Then, type this command on the command line:

 # Linux 
 ugbc.sg1000 bug_data_type.bas -o example.rom
 bluemsx /machine \"SEGA - SG-1000\" /rom1 example.rom
 
 # Windows 
 ugbc.sg1000.exe bug_data_type.bas -o example.rom
 bluemsx  /machine \"SEGA - SG-1000\" /rom1 example.rom

If you have found a problem trying to run this example, if you think there is a bug or, more simply, you would like it to be improved, open an issue for this example on GitHub. Thank you!