Re: No more Foxpro

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I don't know about C++ but C itself compiles very efficiently on many
platforms. Most C instructions don't do much and don't become that many
lines of assembly language. I seem to recall that in the early days C was
even touted as a portable assembler having most of the performance
advantages while still being a higher level language.

Jeff
"Cy Welch" <cywelch@xxxxxxxxx> wrote in message
news:OCpi1jYbHHA.2408@xxxxxxxxxxxxxxxxxxxxxxx
by rewritten do you mean so it's open source? or because it's in C++? The
only other option if you truly want speed would be assembler and for
something large like VFP it would probably be too slow from a development
standpoint. As for rewriting it, I'm not sure how long it would take, or
how many software patents you would violate if you succeeded in actually
duplicating Rushmore and other Fox technologies.

Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com


keyser soze wrote:
fox need to be rewrited

"Cy Welch" <cywelch@xxxxxxxxx> escribió en el mensaje
news:OpRz%234QbHHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
| VFP is written in C++. I'm not sure about the very first versions, but
| from at least 2.0 through 2.6a it was written in Watcom C++. Either
VFP
| 3.0 or 5.0 was the first version compiled in MS C++ (and as I recall
| that was when there was a HUGE increase in size).
|
| I also recall that since that point it had far more compatibility with
| windows since this coincided with a change to using Windows Memory
| handling rather than Watcom's, which while arguably Watcom had better
| memory routines, the MS routines seem to have had less trouble with
| newer versions of Windows.
|
| The FPW 2.6a fast computer problem had something to do with a Watcom
for
| windows compiler routine designed to determine processor speed. Of
| course there was nothing even close to the speeds now, so since they
| started from a specific number and counted down from there then divided
| something else by the result, at about 350 Mhz it broke with a "divide
| by 0" error. Just a touch of trivia.
|
| Cy Welch
| Senior Programmer
| MetSYS Inc
| http://www.metsysinc.com
|
|
| Man-wai Chang wrote:
| >> However, there is a world of difference between programming in C and
| >> programming in XBase. When's the last time you had a heap or stack
| >> problem? Even BASIC with all its similarities is still quite
different.
| >
| > I knew...
| >
| > So VFP was not developed with C++, which makes the data type and
memory
| > allocation issues and easier to handle?
| >


.

Relevant Pages

  • Re: restart after long time
    ... messing around with windows or environments does have me intimidated. ... I enjoyed Pascal programming, disliked the detail of assembly level ... Would like something that compiles rather then ... There are a great number of languages available freely today for most ...
    (comp.programming)
  • Re: restart after long time
    ... messing around with windows or environments does have me intimidated. ... I enjoyed Pascal programming, disliked the detail of assembly level ... Would like something that compiles rather then ... You have a wide choice of languages ...
    (comp.programming)
  • Re: No more Foxpro
    ... Either VFP ... | windows since this coincided with a change to using Windows Memory ... |>> programming in XBase. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: [SLE] Developing a Real Time Data System
    ... The KBasic License is valid for both operating systems: Windows and Linux. ... Modern BASIC language ... chapters learning about the programming language. ...
    (SuSE)
  • Re: Reverse engineering != piracy (was Re: RosAsm disassembler output vs. IDA Pro)
    ... OOPL or fancy "class" keywords to be programming "OOP"...that stuff is ... Rene...one of your RosAsm newbies has just ... under the BASIC language, typing "?" ... surface that works within Windows...but then all "child" windows can ...
    (alt.lang.asm)