HP3000-L Archives

July 1995, Week 4

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:
Ken Sletten b894 c331 x2525 <[log in to unmask]>
Reply To:
Ken Sletten b894 c331 x2525 <[log in to unmask]>
Date:
Tue, 25 Jul 1995 13:18:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
A flyer from Robelle just reminded me of an outstanding
deficiency in HPEDIT and a bunch of other HP subsystems
that are in HP's current HP 3000 Price Guide (I'm not going
to try and remember and list them all).  The deficiency I am
talking about is of course that they don't speak POSIX.
 
$$ SEMI-PLUG (even though we do not have QEDIT) $$
Anyway, the Robelle flyer mentioned that QEDIT now fully
supports the 5.0 HFS: nested directories, long filenames,
and byte-stream files.
$$ END semi-plug $$
 
Lack of POSIX support by various HP subsystems has
been an issue for at least the last two IPROF conferences.
How many years do we have to wait before key HP sub-
systems will support their own HFS ??  Realize that it was
perhaps not reasonable to expect every last sub-system
to support HFS the day HFS was released on the 3000;
but hey, it's been awhile now.
 
And especially since HP bills HPEDIT as their first-line
3000-based editor, still not supporting HFS is really a
glaring hole.  I.e.:  If they haven't done HFS support yet,
one has to wonder how much work they are doing anymore
on HPEDIT.......  Is HPEDIT going down the well-worn
"mature product" path so many other HP products have
followed ??.................  I hope not;  it's a good editor;  our
entire software development team uses it.  But it's got to
keep up with the platform on HFS, or it will very quickly get
sidetracked on a dead end....
 
Ken Sletten

ATOM RSS1 RSS2