Hi, here my wired question again... anybody tried the FIOLIB with PhrozenC? I can't program C, only Z80, so I really don't know how to test it.
I got around to trying PhrozenC today and noticed some superficial differences from Small-C, in my test programme I had from Small-C I had to change the #include statement so the filename was in inverted commas ("") and when I got around to Assembling the resulting Source Code, assembly from the small-c include file had to be altered so hexadecimal begins with the ampersand (&), because PhrozenC uses Maxam or Winape Assembler.
I also noticed that PhrozenC has ditched the ".h" files which Small-C had and simply includes other c header files with addresses defined within. The additional library files PhrozenC uses has changed some of the routines names as well.
During todays experience I was trying to use a Library file I had from Small-C with PhrozenC, but in frustration I chucked it out and focused on the PhrozenC Libraries instead. Most of the stuff I needed was present, one of the routines I had to modify from the original Small-C 'putchar();' and I was able to include other routines to generate Random Numbers and simple Screen Scrolling using SCR HW ROLL.
The only other trouble I had was trying to Redefine Characters working and I wanted to setup a Place using an Array to hold the Matrix Data (PhrozenC's way of saying SYMBOL AFTER xxx) to cater for more Redefined Graphics. Eventually I managed to get one working with the Array by looking at how other Firmware Library routines handled it when HL & DE registers were POPed and PUSHed before CALLing their relevant routines, and all I had to do was specify from which Character Number I wanted to use and point to the Name of the Array (without specifying a specific spot).
The Generated Assembly file was 12kb in size, with a number of extra routines chucked in for the Ride, though even when I finally got the code working, I was still poking about with the Source Code, changing ints to char which didn't seen to bother PhrozenC in the context of having Integer based combining with Char byte types. Once I was happy with the final code, the resulting StarScrl Demo was just over 700 bytes in length.