HP3000-L Archives

August 1998, Week 2

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:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Thu, 6 Aug 1998 09:35:05 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (84 lines)
Eric,

As others have already mentioned, FOPEN is an integral part of MPE and can
never go away or MPE will be dead in the water. I believe the main reason
that people still program using the older intrinsics is because much of
the programming is maintenance programming on existing applications. There
is no strategic advantage to re-coding an existing FOPEN to be an HPFOPEN.
To do so would require decoding the bit masks and translating the results
into the new parameters, potentially breaking the code. IOW, if it ain't
broke don't fix it.

In fact the same reasons can apply to new software development as well.
Many programmers, myself included, are lazy by nature and would rather
borrow a working piece of code than write something from scratch.

Doug Werth                                     Beechglen Development Inc.
[log in to unmask]                                       Cincinnati, Ohio

The opinions expressed do not necessarily represent the views or opinions
of Beechglen Development. They might, but not necessarily. They represent
solely the opinions of the author.

-----Original Message-----
From: Eric Kundl <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Thursday, August 06, 1998 6:13 AM
Subject: Re: EASY QUESTION COMMAND INTRINSIC


>in all my code i display the "command" being issued without the "%15" if
>there is a non-zero err-flag. sometimes by looking at the actually issued
>command it becomes obvious why it failed. usually in my applications its
>because i assembled a file eq incorrectly with an extra space somewhere.
if
>the command looks ok, the try it at the command prompt manually and see
what
>you get.
>
>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?
>
>--
>thanks........eric kundl
>NylCare IS - manager/programmer
>ICQ: 3154765
>[log in to unmask]
>[log in to unmask]
>http://www.netcom.com/~ekundl/
>
>Johnson Stephen wrote in message ...
>>statement pic x(50) followed by %15
>>param S9(4) COMP
>>err      S9(4) COMP.
>>
>>I am calling intrinsic "COMMAND" using statement, param, err.
>>
>>The err coming back is  -0007
>>
>>Can someone tell me what -0007 means.
>>
>>?????
>>
>>thx
>>
>>
>>
>>Stephen  Johnson
>>

ATOM RSS1 RSS2