HP3000-L Archives

August 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Zoltak <[log in to unmask]>
Reply To:
John Zoltak <[log in to unmask]>
Date:
Thu, 6 Aug 1998 08:23:35 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Eric Kundl wrote:
>btw, i notice a lot of programmers are still using the older intrinsics
when
>there are native mode equivalents available. HPCICOMMAND in this case
could
>have been used instead. And there is HPFOPEN rather than FOPEN, plus
lots of
>others.  So my question is: if an application will never see an old MPE
cpu,
>will only be run on an MPEiX cpu, is there any reason to not use the
newer
>intrinsics? or are we talking about some resistance to change here? i
find
>HPFOPEN much easier that FOPEN to use without the bit maps etc...
these
>newer intrinsics have been around for years and i expect the older ones
to
>disappear sometime.. maybe with the new 64bit cpu"s???
>What do the rest of you think?

I think that old habits die hard. Some just don't want to learn new
things. As far as FOPEN going away, I don't think so. Even parts of
Mpe/iX use FOPEN. And as long as we have compatibility mode there's no
way these older intrinsics are leaving.

John Zoltak
North American Mfg Co

ATOM RSS1 RSS2