Topic: Standard-conforming C++ compilers on PC (that will do Window=
Author: James Kuyper <kuyper@wizard.net>
Date: 1998/09/16 Raw View
devphil@my-dejanews.com wrote:
>
> In article <35f99d8d.0@news.new-era.net>,
> scott@softbase.com wrote:
> > devphil@my-dejanews.com wrote:
> >
> > > Since you have to use their API
> > > anyway, just use all of it and save yourself some trouble.
> >
> > It is possible to create code in such a way that the user interface is
> > separate from the internals. Such code could be easily ported. I
> > disagree that developing software for Windows means portability is not
> > required.
How feasible it is to do that, depends upon how deeply the GUI affects
your code. If most of your code is devoted to Windows operations, as for
example in game programs and various kinds of file editors, you can't
gain much by seperating out the GUI-independent features.
> Such as wrappers for system calls, concurrent programming, network
> programming, /every/ kind of end-user interface except for std{in,out,err}
> (like any app running in a DOS box is going to sell well to Windows users).
It sounds like most of your code does involve Windows, so seperating out
the non-Windows part won't gain you much.
Other kinds of applications, such as data analysis facilities, are
dominated by complicated system-independent processing. The GUI serves
only to get the user's input on how the processing should be done, and
to report the results. That is the kind of code that ports most easily
to a new GUI.
[ comp.std.c++ is moderated. To submit articles, try just posting with ]
[ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ]
[ --- Please see the FAQ before posting. --- ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]