Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Converting Clipper to “C” on a DOS platform looks mighty attractive to me?

0
Posted

Converting Clipper to “C” on a DOS platform looks mighty attractive to me?

0

Not for 16-bit systems! When you take into account all the pros and cons, this no longer looks anywhere near as attractive as it does at first thought. DOS has such memory limitations that it is not practical to do such a thing. There are other products that do portions of this task, such as X2c, CodeBase, or Force, among others. But due to the memory limitations they are nowhere as complete a product as FlagShip. It is like comparing a Ford Pinto to a Cadillac. True Executable code is almost always larger than Psuedo code with an embedded interpreter such as Clipper is. Our executables are about three times the size on the average as Clipper’s. Even the smaller Clipper executable has terrible problems with memory management, and we are not willing to play those games. Not when we can give you something much better. The idea of FlagShip is to allow the language that makes you productive, to let you work in Unix with very little additional knowledge. All this in an environment that also

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123