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:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Fri, 7 Aug 1998 12:32:49 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
On Aug 4, 12:58pm, 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.

Both COMMAND and HPCICOMMAND are NM intrinsics.  They also differ in
behavior: COMMAND should be used for system "services", like building
or purging a file.  HPCICOMMAND should be used when a program wants to
allow CI-like access to its users.  COMMAND does not search for UDCs;
whereas, HPCICOMMAND does.  And, there are a few other differences.

> ...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?

In some cases the "older" interface is easier/simplier to call.
BTW, FOPEN is also a NM intrinsic.

Regards,
Jeff Vance, CSY


--

ATOM RSS1 RSS2