Someone else must have mentioned 'C' along the way, since I'm not a 'C' afficionado. I don't know what programming an MCU in HLL would have to do with converting code from 8035 (the romless 8048) which is apparently what the O/P has to deal with, and 8031 (the romless 8051) which is what he seems to want to use.

Once it was on the table, however, it seemed reasonable to point out that, if one wanted to use any of the features that make 'C' convenient, one would end up with entirely too much code space used. Now, I know that modern 805x components have more than the 1KB code space that the 8048 offers, and I know that code space is fairly inexpensive in modern 805x's. That, in fact, is what has made for the popularity of HLL's as opposed to carefully crafted ASM in which every line of code is both time- and space-constrained. Most coders don't care that their employer/client has to buy the next-larger MCU because he didnt want to whittle down his work product. They don't care because the cost isn't that large and its unlikely to be noticed. However, I consider it unconscionable to ask one's client to buy an MCU with 64KB of code space on-chip when, with a little extra effort, the code size could fit in 32 KB, as is often the case when one uses a HLL and the associated libraries.

RE