HP3000-L Archives

March 1999, 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:
Ted Ashton <[log in to unmask]>
Reply To:
Ted Ashton <[log in to unmask]>
Date:
Tue, 2 Mar 1999 18:29:04 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
Greetings,

Not sure if this is an SPL or an FREAD question.  I'm calling FREAD from SPL
and handing it the byte array WORK.  WORK is defined in the globals (many) at
the top of the program as BYTE ARRAY WORK(*) = WORKL and WORKL is defined
previous to that as ARRAY WORKL(0:128).   If those definitions are near the top
of the global definitions, it has a small address (I'm printing the value of
@WORK in my debugging code) and seems to work beautifully.

On the other hand, if it is defined later on (where it has a fairly large
address, large enough that ASCII thinks it is negative), FREAD returns with an
error 73, bounds violation.  Now WORK is used fairly heavily throughout the
program and doesn't seem to cause trouble anywhere else.  I don't understand,
quite, why one works and the other doesn't, I'd expect it to die everywhere if
it's going to die anywhere.  There isn't some bounds checking that I need to
turn on like in COBOL, is there?

TIA,
Ted
--
Ted Ashton ([log in to unmask]), Info Serv, Southern Adventist University
          ==========================================================
It is hard to know what you are talking about in mathematics, yet no one
questions the validity of what you say. There is no other realm of discourse
half so queer.
                        -- Newman, James R.

ATOM RSS1 RSS2