Re: Called Module with File Access - where to Close

> You're correct. But it's a big "IF." I've developed systems on big iron to
> PCs. I've never met a manager who was concerned about porting a new
> development to a yet-unknown hunk of hardware in the amorphous future. Such
> managers COULD exist, but I suspect no one pays them much mind anyway.

My most previous job developed in MicroFocus on the PC and the code had
to be portable to everything from MVS/VSE/IMS , iSeries, 5 flavors of
UNIX, Linux, and even some Dec VMS. (They dropped UnisysA about 18
months ago) So we really cared about portability from the VP level
down. There were a number of MicroFocus extensions that we would have
loved to use but couldn't because of the other platforms.

.

Relevant Pages

  • Re: Whither VMS?
    ... How can a simple user app crash the system? ... A user app written in C has not more control than if it were written ... If portability is the prime directive, ... Same goes for early support of new stuff (GPUs and Cell Engines come to mind). ...
    (comp.os.vms)
  • Re: <ctype.h> toLower()
    ... > brains knows that all software is designed with a specific target platform ... > in mind. ... which is why portability is /so/ important. ...
    (alt.comp.lang.learn.c-cpp)
  • Re: esound and alsa not compatible?
    ... > to mind. ... > from a programmers point of view and it will be clear that even with ... a good sound daemon is important. ... If it was just a question of portability, ...
    (Debian-User)
  • Re: looking for good shell programming books?
    ... mind for purposes of portability. ...
    (Fedora)