Racemaniac
Scorched GP programmer
we all discover strange things that shouldn't do what they do, or that simply don't work.
lets group all those things, cause if we all keep it to ourselves it's a lot of information lost
things i know so far:
1. the split command doesn't work on the gp32
2. let_me_alone() doesn't kill the father process of the process that uses it, i don't know about other processes...
3.unlike java, where i got quite some experience, the initialisation of an array (array[2] for example) reserves memory for a number of elements up to the index given, not like in java for the given number of elements, so in fenix array[2] will give an array of 3 elements, in java it would be one of 2 elements.
4.fenix has a strange way of rounding numbers,it just gets rid of the decimals (so 5.99 becomse 5), main problem with this is for example when you use the advance command, it does the same with angles... and since there are a limited number of directions you can move in it can be disturbing (was visible in quiest's minigame project, the sliding game's "disc" had a drift to the left because of this)
5.when stopping a song, and unloading it, make a little waitloop in between, or you'll get noise...
6.fenix has no protection against arrays going beyond their values, if you habe the array initialised as array[5], and write in the code array[6]=...., the compiler will give an arror, but if you use array, and i gets for example the value six, you'll have a typical pointer overflow, no telling what will happen...
lets group all those things, cause if we all keep it to ourselves it's a lot of information lost
things i know so far:
1. the split command doesn't work on the gp32
2. let_me_alone() doesn't kill the father process of the process that uses it, i don't know about other processes...
3.unlike java, where i got quite some experience, the initialisation of an array (array[2] for example) reserves memory for a number of elements up to the index given, not like in java for the given number of elements, so in fenix array[2] will give an array of 3 elements, in java it would be one of 2 elements.
4.fenix has a strange way of rounding numbers,it just gets rid of the decimals (so 5.99 becomse 5), main problem with this is for example when you use the advance command, it does the same with angles... and since there are a limited number of directions you can move in it can be disturbing (was visible in quiest's minigame project, the sliding game's "disc" had a drift to the left because of this)
5.when stopping a song, and unloading it, make a little waitloop in between, or you'll get noise...
6.fenix has no protection against arrays going beyond their values, if you habe the array initialised as array[5], and write in the code array[6]=...., the compiler will give an arror, but if you use array, and i gets for example the value six, you'll have a typical pointer overflow, no telling what will happen...