The SX does not have built-in Basic. It runs externally on your PC and comipiles Basic statements to SX instructions.
And I may be a bit of a lone wolf here, but I would not neccessarily use some pre-canned drivers out of ROM. To date I have always written everything myself (possibly by studying others' code) so that I get exactly what I want. For example, I see your assessment on the size of a serial driver at 2KB, and I think that is a horribly bloated figure, probably brought on by being (in my opinion) too general where more specific and concise code would do a much better job, albeit more work and more complicated for beginners. By the same token I fear that most pre-canned routines in ROM (other than floating point math) would exhibit similar bloat and cause poor performance. The serial (and other) drivers I have written come in at a couple of dozen bytes for simple ones, and double to triple that for more complicated ones. Similarly for I2C, SPI routines. I like to run my code very tight, and get enhanced performance out of that.
So my take on all this is to have everyting as simple and flexible as possible that way everyone can tailor things the way they see fit, and get the performance they seek.
Comments
The SX does not have built-in Basic. It runs externally on your PC and comipiles Basic statements to SX instructions.
And I may be a bit of a lone wolf here, but I would not neccessarily use some pre-canned drivers out of ROM. To date I have always written everything myself (possibly by studying others' code) so that I get exactly what I want. For example, I see your assessment on the size of a serial driver at 2KB, and I think that is a horribly bloated figure, probably brought on by being (in my opinion) too general where more specific and concise code would do a much better job, albeit more work and more complicated for beginners. By the same token I fear that most pre-canned routines in ROM (other than floating point math) would exhibit similar bloat and cause poor performance. The serial (and other) drivers I have written come in at a couple of dozen bytes for simple ones, and double to triple that for more complicated ones. Similarly for I2C, SPI routines. I like to run my code very tight, and get enhanced performance out of that.
So my take on all this is to have everyting as simple and flexible as possible that way everyone can tailor things the way they see fit, and get the performance they seek.
Cheers,
Peter (pjv)