> Thanks for the lesson in C/C++. I have a son-in-law working=20
> for the most pretegious gaming company in California. He=20
> said that once he has that experience on his resume, he would=20
> be able to go to work anywhere in the country. He and my=20
> Daughter will be return to Texas in about another year. They=20
> plan to move to Dallas. Anyway, he said that the companies=20
> he worked for does not allow C++ period. Its to slow. Of=20
There's more truth in VFP being obsolete.
> course there nothing faster than assembler, if you can get it=20
> to run. Its a little difficult to degug from what I've heard.
The great thing with C++(and I think C), is you can put assembler =
in-line in your code. This way you can do a specific loop or calculation =
in the absolute, most optimized(according to the developer) assembly =
possible-- and the compiler will just wrap it into your code untouched. =
I also see this quite often for MMX/SSE/SSE2 instructions...
> I suppose anyone could write an application from scratch=20
> without going the C++ route. However, could you imagine=20
> needing to write your own classes/libraries. It could take a=20
> couple of years just to write the foundation classes to an=20
> application before you ever even got around to writing the=20
> first line of the app.
There are many toolkits available for this.
> Of course Linux has some of these same issues. The KDE=20
> destop is much more mature than gnome. Since Linux is open,=20
> one could use the KDE classes/libraries to develop an=20
> application. I read an article a couple of years ago about=20
> whether it would be best to build an application using KDE or=20
> Gnome. At that time the Auther said that it could be=20
> necessary to spend a couple of year on the foundation to your=20
> app before you even begin the app itself, if you went the=20
> Gnome route. However, Gnome was technically more corect that=20
> KDE. Hopefully Gnome has mature since I read the article.
Paul McNett was mentioning something about a QT toolkit. I believe this =
offered a common library to develop X-windows apps with.
> Would it be possible to port Visual FoxPro to Linux/Unix if=20
> the source code were made available, and what difficulties=20
> would you expect to encounter?
Yes. All Win32 API calls would need to be changed to the appropriate =
UNIX calls, and any Microsoft-specific C/C++ language extensions(there =
are not many), if used in VFP source, would have to be converted to the =
equivelent in the compiler used on *nix.
--=20
Derek
©2003 Derek J. Kalweit |
