HP3000-L Archives

October 1997, Week 3

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:
Steve Dirickson b894 WestWin <[log in to unmask]>
Reply To:
Steve Dirickson b894 WestWin <[log in to unmask]>
Date:
Fri, 17 Oct 1997 14:09:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (15 lines)
<<You're right, Steve, you not only can't have duplicate XL names, but if
you put XL.PUB.SYS and/or NL.PUB.SYS in the string they have to be at the
end. That's as of 5.0; in MPE/iX they could come earlier in the string.>>


Since this seems to bite people on a recurring basis, can anyone (Jeff?)
shed any light on the reason for this "no repeats" restriction? I can see
the reasons for some of the other rules, like the privilege-level
sequencing rule. But I have seen a number of places where a re-scan of a
given XL, maybe a system XL or maybe a product-specific one, would be
really handy. Static linkers can handle the situation; why not load-time
or run-time resolution? Thanks.

Steve

ATOM RSS1 RSS2