Re: size_t problems
- From: santosh <santosh.k83@xxxxxxxxx>
- Date: Mon, 03 Sep 2007 01:13:26 +0530
Malcolm McLean wrote:
"Kelsey Bjarnason" <kbjarnason@xxxxxxxxx> wrote in message
news:cl9rq4-8cc.ln1@xxxxxxxxxxxxxxxxxxxxxxx
On Sat, 01 Sep 2007 20:16:43 +0100, Malcolm McLean wrote:What you not uncommonly find is that the actual processing that the app
No, limited experience, Not the same thing as incompetence at all.
If you write say, mainly code to drive GUIs under Windows, you will find
>> that there's little point making much portable. Everything has to be
ripped
up and rewritten whenever the denizens of Redmond decide to realease a
new compiler anyway.
He said incompetence, and you just demonstrated it.
If I were writing such apps, I'd write the body of the code to be as
conforming as possible, meaning it is effectively immune to switching to
a different OS, compiler, or version of a compiler.
performs is trivial - maybe it adds a few columns of numbers together and
produces a report. However the GUI to allow the user to enter these
numbers, check them, specify which columns to add up, and format the
report might be very non-trivial. So in fact the portable bit of the code
is a sum() function and maybe a few histogram or pie chart generators,
without the graphical part.
You can always write your own wrappers for platform specific GUI
functionality. Things like Java's Swing and wxWidgets prove that it can be
done. Of course it still won't be as portable as C code using only Standard
facilities, *and* it's likely to be a lot of work, but it's possible.
.
- References:
- Re: size_t problems
- From: Ben Bacarisse
- Re: size_t problems
- From: Malcolm McLean
- Re: size_t problems
- From: Richard Heathfield
- Re: size_t problems
- From: Ed Jensen
- Re: size_t problems
- From: Martin Wells
- Re: size_t problems
- From: Ed Jensen
- Re: size_t problems
- From: Martin Wells
- Re: size_t problems
- From: Malcolm McLean
- Re: size_t problems
- From: Kelsey Bjarnason
- Re: size_t problems
- From: Malcolm McLean
- Re: size_t problems
- Prev by Date: Re: size_t problems
- Next by Date: Re: How to force fscanf to find only data on a single input line?
- Previous by thread: Re: size_t problems
- Next by thread: Re: size_t problems
- Index(es):
Relevant Pages
|