| Title: | "ASK THE WIZARDS" |
| Moderator: | QUARK::LIONEL |
| Created: | Mon Oct 30 1995 |
| Last Modified: | Mon May 12 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1857 |
| Total number of notes: | 3728 |
Return-Path: "VMS001::WWW"@vms001.das-x.dec.com Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX); Tue, 22 Apr 1997 09:06:08 -0400 Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV) id IAA28788; Tue, 22 Apr 1997 08:52:31 -0400 (EDT) Date: Tue, 22 Apr 1997 07:56:12 -0400 Message-Id: <[email protected]> From: "VMS001::WWW"@vms001.das-x.dec.com (22-Apr-1997 0756) To: [email protected], [email protected], [email protected] Subject: Ask the Wizard: '[email protected]' X-VMS-To: [email protected] Remote Host: tmesis.com Browser Type: Mozilla/3.0b5Gold (X11; I; OpenVMS E7.1 AlphaStation 200 4/166) Remote Info: <null> Name: Brian Schenkenberger Email Address: [email protected] CPU Architecture: VAX and Alpha Version: v 6.2 Questions: This question deals with both OpenVMS platforms. Why is LIB$FIND_IMAGE_SYMBOL not available in object form in STARTLET.OLB? Can an OpenVMS Alpha and VAX version of this routine be made available in object form? An expedient response will be graciously appreciated. I am current using the $IMGACT system service to merge the LIBRTL into process space and then, I locate the transfer vecotr for LIB$FIND_IMAGE_SYMBOL to call to merge all of the other routines I need to locate. I'd really like to NOT use this code and simple call an object version of the routine maintained by DEC. Thank you in advance.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1790.1 | Will Be Considered For Inclusion in Future Release | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Apr 29 1997 14:51 | 15 |
Availability of the LIB$FIND_IMAGE_SYMBOL module in object format will be considered for inclusion in a future OpenVMS release -- however, given the entirely undocumented and changeable nature of the underlying interfaces called by the LIB$FIND_IMAGE_SYMBOL routine, it may not be feasible to support this. Updates have been made in V7.1 (and V7.0, with ECO), to allow the LIB$FIND_IMAGE_SYMBOL call to resolve system service entry points. For support, one must link on the oldest OpenVMS release one plans to support. As an unsupported but sometimes useful alternative, consider linking against the oldest version of the LIBRTL you plan on running against. | |||||