HP3000-L Archives

February 2001, 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:
Ken Hirsch <[log in to unmask]>
Reply To:
Ken Hirsch <[log in to unmask]>
Date:
Tue, 6 Feb 2001 11:45:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
I know there has been some discussion about this before, but I don't see the
answer to the question I have about extensible intrinsic calls.  The first
parameter to HPCIGETVAR is the parameter count, but when I tried passing
fewer than 14 arguments and set parm_ct accordingly, it didn't always work.
With HPCIGETVAR this is only mildly annoying, but I'm about to code HPFOPEN
and I'd rather not have to include 80 zeros in the call.

What's the deal?  Is this number supposed to be the total number of
parameters passed, the number of optional parameters, the number of
bytes/halfwords/words?

I guess I could get this information using the system debugger and see what
code the official compilers produce, but since I don't know Precision
Architecture or the system debugger, I thought I'd ask here first.

By the way, is there an easy way to get an assembly listing of a
program/NMOBJ/etc.?


Ken Hirsch

ATOM RSS1 RSS2