DOCSLIB.ORG

Lecture #1 Introduction to Perl Introduction Perl Is Acronym Of

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lecture #1 Introduction to Perl Introduction Perl Is Acronym Of Lecture #1 Introduction to Perl Introduction Perl is acronym of “Practical Extraction and Report Language”. It is a scripting language developed by Larry Wall in the late 1987 as a Unix-based report language. However, it has evolved to be one fo the popular Web programming languages. According to the Perl.org site, which develops and maintains the language, Perl is “intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal). Its major features are that it is easy to use, supports both procedural and object-oriented (OO) programming, has powerful built-in support for text processing, and “has one of the world’s most impressive collections of third-party modules.” As of the time this lecture note is written, Perl 5 is the latest stable version. The latest major stable revision of Perl 5 is 5.24.0, which is released in May 09, 2016. There is, however, Perl 6 which is still under development. According to the Perl.org web site, Perl 6 is a sister language, part of the Perl family, not intended as a replacement for Perl 5, but as its own thing - libraries exist to allow you to call Perl 5 code from Perl 6 programs and vice versa. The final release date of Perl 6 is unknown. Tools need for Perl is not part of Windows operating system. Students using Windows OS need to built the this class “toolkit” individually in order to complete all the learning activities of this course. The toolkit includes: (a) a Perl distribution, (b) a web server, (c) a generic text editor, and (d) an optional but recommended USB flash drive (with 2GB of free speace). While a nearly-zero cost solution is provided by the instructor as part of the learning activities in this lecture, this section will explain why the toolkit is required. Perl distribution is available for a wide variety of platforms, including Windows, Linux, and Mac. This lecture note is written based on Windows operating systesm. Students will need to download the either the 32-bit or 64-bit binary code applicable for their platforms and install Perl. The official site to download Perl is http://www.perl.org/. Due to the need to discuss Perl for Web programming, the instructor chooses to use XAMPP which is a handy tool with Perl included. XAMPP is an open-source web server package that works on various platforms. It is actually an acronym with X meaning “cross” platform, “A” for Apache HTTP server, “M” for MySQL, “P” for PHP, and “P” for Perl. XAMPP was designed to help webpage developers, programmers, and designers check and review their work using their computers even without connection to the web or internet. The latest version of XAMPP is available for downloading at https://www.apachefriends.org/index.html. By the way, the entire XAMPP can be installed into and executed from a USB flash drive. = Apache + MySQL + PHP + PERL 1 The good news is: Perl can run in most major operating systems, including Linux/ Unix, Microsoft Windows, Mac OS X, and others. Perl also supports most of the web server software including Apache, Microsoft Internet Information Server, Personal Web Server, Netscape, iPlanet servers, and many others. However, it is not techinically practical for the instructor to provide every student a functional Web server. In the past, students need to download and install a Web server application, such as Apache. Then, each student need to: (a) download and install Perl installer, (b) activate supports for Perl, and (c) modify the server’s configuration files in order to recognize Perl script files before they can write and test Perl scripts. On the other hands, in order to learn how a Perl server works with MySQL server in order to build a data-driven site, students also need to download and install the MySQL software, which is a popular choice of database management system (DBMS) used in the World Wide Web. Thanks to the generosity of ApacheFriends.org which provides XAMPP for free, students are now able to execute PHP scripts without all the above mentioned preparations. XAMPP is a free and open source cross-platform web server package, consisting mainly of the Apache HTTP Server, MySQL database, and interpreters for scripts written in the Perl. Throughout this course, students will be using XAMPP to test and execute Perl scripts. The lastest version of XAMPP can be downloaded at https://www.apachefriends.org/. With XAMPP installed, each student’s personal computer (including laptop) becomes an individual web server that can interpret PHP codes and is able to execute query statements to retrieve data from a MySQL database. XAMPP = client + Web server + PERL server + MySQL server The following figure illustrates the role MySQL plays. Perl scripts is the intermediary between the web browser and the MySQL server. The browser is the data requester, while MySQL is the data provider. The communication between the browser and the web server is handled by Perl. Likewise, the communication between the web server and MySQL is done by Perl as well. Interestingly, the user interface between the user (human) and the web server must be defined with HTML (Hypertext Markup Language), which is a standardized system for tagging text files to achieve font, color, graphic, and hyperlink effects on World Wide Web pages. dynamic web web content data web manipulation browser MySQL HTTP request server database In a nutshell, a dynamic web site can be constructed by using Perl to build the application, while using HTML to define the web content layouts. The following illustrates the relationship between Perl and HTML. One can say that HTML is at the human layer, while Perl is only at the Perl. The good news is: Throughout this course, students will focus on the learning of Perl coding, not the building of fancy-looking web sites using HTML and CSS (cascade style sheet). After all, this is a web programming course, not a web development course. 2 In a nutshell, a dynamic web site can be constructed by using Perl to build the application, while using HTML to define the web content layouts. The following illustrates the relationship between PERL and HTML. One can say that HTML is at the human layer, while Perl is only at the Perl. The good news is: Throughout this course, students will focus on the learning of PERL coding, not the building of fancy-looking web sites using HTML and CSS (cascade style sheet). After all, this is a web programming course, not a web development course. HTML human user PERL machine In this class, due to the barriers for the instructor to build a server that allows students to upload scripts and test these scripts with the server, XAMPP is probably the best alternative. Students will install a copy of XAMPP, which is a scaled-down version of Apache Web server, on a local machine (or a USB flash drive). The next few sections will discuss how Perl dynamically generate output for command-line interfaces (such as the Microsoft Command Prompt and Linux Terminal) and web broswers. By the way, a command line interface (cli) is a user interface to a computer’s operating system or an application in which the user responds to a visual prompt by typing in a command on a specified line, receives a response back from the system, and then enters another command, and so forth. Throughout this course, the instructor chooses to use Microsft Command Prompt for demonstration. Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. C:\Users\user> As a matter of fact, programmers can run Perl from a graphical user interface (GUI) environment as well. Some use Padre (a Perl IDE); others use Eclipse Plugin EPIC (Perl Editor and IDE for Eclipse if you are familiar with Eclipse). However, throughout this course, a generic text editor like Microsoft Notepad is good enough. Perl supports several file extensions; however, programmers typically use .pl for regular Stand- alone Perl scripts and .pl or .cgi for Web scripts, while Perl modules use .pm. A Perl “module” is a set of related functions in a single library file with .pm extensions. Throughout this course, students will mainly create stand-alone Perl scripts use the .pl extension. What is a Perl Perl is a scripting language. All Perl programs do not need to be compiled into self-excutable program? programs (such as .exe). They stay as text-based script files designed to be read by the Perl interpreter. Each time when a Perl script is called for execution, it is the Perl interpreter that converts the script file contents to machine codes (binary codes). The text-to-binary convesrsion is done each time when the script files are read. Unlike most programming languages (such as C++), Perl script files are not required to be compiled into self-executable programs. However, there are some utilities that can compile Perl scripts into standalong executables (read for http://www.nicholassolutions.com/tutorials/perl-PAR.htm details). The following figure illustrates how a Perl script is interpreted and its two possibly routines of output. 3 Command-line interface Perl Perl scripts interpret Web server Web browser (Apache) (GUI) In a nutshell, Perl scripts perform a combination of three primary tasks, Inpute, Processing, and Output, known as the I-P-O model. The following is a simple Perl script that performs both processing and output. It generates a text message as output: Hello, world!. In this program, the instructor did not use any control structure (such as if..else or for loop); therefore, all its statements will be read sequentially (in a line-by-line manner).
Load more

Recommended publications
  • Operating System Engineering, Lecture 3
    6.828 2012 Lecture 3: O/S Organization plan: O/S organization processes isolation topic: overall o/s design what should the main components be? what should the interfaces look like? why have an o/s at all? why not just a library? then apps are free to use it, or not -- flexible some tiny O/Ss for embedded processors work this way key requirement: support multiple activities multiplexing isolation interaction helpful approach: abstract services rather than raw hardware file system, not raw disk TCP, not raw ethernet processes, not raw CPU/memory abstractions often ease multiplexing and interaction and more convenient and portable note: i'm going to focus on mainstream designs (xv6, Linux, &c) for *every* aspect, someone has done it a different way! example: exokernel and VMM does *not* abstract anything! xv6 has only a few abstractions / services processes (cpu, mem) I/O (file descriptors) file system i'm going to focus on xv6 processes today a process is a running program it has its own memory, share of CPU, FDs, parent, children, &c it uses system calls to interact outside itself to get at kernel services xv6 basic design here very traditional (UNIX/Linux/&c) xv6 user/kernel organization h/w, kernel, user kernel is a big program services: process, FS, net low-level: devices, VM all of kernel runs w/ full hardware privilege (very convenient) system calls switch between user and kernel 1 good: easy for sub-systems to cooperate (e.g. paging and file system) bad: interactions => complex, bugs are easy, no isolation within o/s called "monolithic";
    [Show full text]
  • The Design of a Pascal Compiler Mohamed Sharaf, Devaun Mcfarland, Aspen Olmsted Part I
    The Design of A Pascal Compiler Mohamed Sharaf, Devaun McFarland, Aspen Olmsted Part I Mohamed Sharaf Introduction The Compiler is for the programming language PASCAL. The design decisions Concern the layout of program and data, syntax analyzer. The compiler is written in its own language. The compiler is intended for the CDC 6000 computer family. CDC 6000 is a family of mainframe computer manufactured by Control Data Corporation in the 1960s. It consisted of CDC 6400, CDC 6500, CDC 6600 and CDC 6700 computers, which all were extremely rapid and efficient for their time. It had a distributed architecture and was a reduced instruction set (RISC) machine many years before such a term was invented. Pascal Language Imperative Computer Programming Language, developed in 1971 by Niklaus Wirth. The primary unit in Pascal is the procedure. Each procedure is represented by a data segment and the program/code segment. The two segments are disjoint. Compiling Programs: Basic View Machine Pascal languag program Pascal e compile program filename . inpu r gp output a.out p t c Representation of Data Compute all the addresses at compile time to optimize certain index calculation. Entire variables always are assigned at least one full PSU “Physical Storage Unit” i.e CDC6000 has ‘wordlength’ of 60 bits. Scalar types Array types the first term is computed by the compiler w=a+(i-l)*s Record types: reside only within one PSU if it is represented as packed. If it is not packed its size will be the size of the largest possible variant. Data types … Powerset types The set operations of PASCAL are realized by the conventional bit-parallel logical instructions ‘and ‘ for intersection, ‘or’ for union File types The data transfer between the main store buffer and the secondary store is performed by a Peripheral Processor (PP).
    [Show full text]
  • Entry Point Specification
    EMV® Contactless Specifications for Payment Systems Book B Entry Point Specification Version 2.6 July 2016 © 2016 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV Contactless Book B Entry Point Specification version 2.6 Legal Notice The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology.
    [Show full text]
  • Openshift Container Platform 3.11 CLI Reference
    OpenShift Container Platform 3.11 CLI Reference OpenShift Container Platform 3.11 CLI Reference Last Updated: 2021-04-12 OpenShift Container Platform 3.11 CLI Reference OpenShift Container Platform 3.11 CLI Reference Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • HP Openvms Utility Routines Manual
    HP OpenVMS Utility Routines Manual Order Number: BA554-90019 June 2010 This manual describes the OpenVMS utility routines, a set of routines that provide a programming interface to various OpenVMS utilities. Revision/Update Information: This manual supersedes the HP OpenVMS Utility Routines Manual, OpenVMS Alpha Version 8.3. Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.4 Hewlett-Packard Company Palo Alto, California © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ZK4493 The HP OpenVMS documentation set is available on CD. This document was prepared using DECdocument, Version 3.3-1B. Contents Preface ............................................................ xvii 1 Introduction to Utility Routines 2 Access Control List (ACL) Editor Routine 2.1 Introduction to the ACL Editor Routine ........................... ACL–1 2.2 Using the ACL Editor Routine: An Example ....................... ACL–1 2.3 ACL Editor Routine . ........................................ ACL–2 ACLEDIT$EDIT ...........................................
    [Show full text]
  • Command Line Interface Overview
    Command Line Interface Overview Note The ASR 5000 hardware platform has reached end of life and is not supported in this release. Any references to the ASR 5000 (specific or implied) or its components in this document are coincidental. Full details on the ASR 5000 hardware platform end of life are available at: https://www.cisco.com/c/en/us/products/collateral/wireless/asr-5000-series/eos-eol-notice-c51-735573.html. This chapter describes the numerous features in the command line interface (CLI). It includes information about the architecture of the CLI, its command modes and user privileges, how to obtain help within the CLI, and other key items. The operating system (StarOS™) controls the overall system logic, control processes, and the CLI. The CLI is a multi-threaded user interface that allows you to manipulate, configure, control and query the hardware and software components that make up the system and its hosted services. In addition, the CLI can host multiple instances of management and service configuration sessions. This allows multiple users to simultaneously access and manage multiple hosted services. This section provides the following information about the CLI: • CLI Structure, on page 1 • CLI Command Modes, on page 2 • CLI Administrative Users, on page 2 • CLI Contexts, on page 7 • Understanding the CLI Command Prompt, on page 8 • CLI Command Syntax, on page 9 • Entering and Viewing CLI Commands, on page 9 • Obtaining CLI Help, on page 13 • Exiting the CLI and CLI Command Modes, on page 14 • IP Address Notation, on page 15 • Alphanumeric Strings, on page 16 CLI Structure CLI commands are strings of commands or keywords and user-specified arguments that set or modify specific parameters of the system.
    [Show full text]
  • 1 Introduction to C – Part I
    1 Introduction to C – part I In this class, we will be employing the modern “C” language which is com- 1 monly used for scientific programming . “C” is closely related to C++ which is an Object Oriented language. It turns out that, while occasionally useful, the Object Oriented properties of C++ are not required for most types of scientific programming. In addition, acquiring a working knowledge of C++ can involve quite a steep learning curve. The object of this class is to get you up to speed as rapidly as possible in a powerful and versatile programming language (we have about three weeks to do that!) and then to introduce you to a number of numerical techniques useful and essential for work in physics and engineering. As it turns out, many software programming pack- ages, such as MathCad and IDL, have syntaxes that are very similar to “C”, and so learning “C” is an excellent entry point for a host of other program- ming environments. Some of you will already have a working knowledge of C or C++. If you don’t, the following three chapters will get you started. Otherwise, consider them a quick refresher. Read: The C Programming Language: Chapter 1. 1.1 Computer Memory and Variables Basically speaking, a computer program is a series of statements that manip- ulate data stored in the computer’s memory and yields a (hopefully useful) result. One can think of the memory of a computer as a series of boxes, each of which can contain one piece of data (a number, a character, etc.).
    [Show full text]
  • Linux Kernel Initialization
    Bootlin legacy Linux kernel training materials Linux kernel initialization This file is an old chapter of Bootlin’ embedded Linux kernel and driver development training materials (https://bootlin.com/training/kernel/), which has been removed and is no longer maintained. PDF version and sources are available on https://bootlin.com/doc/legacy/kernel-init/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/1 Rights to copy © Copyright 2004-2018, Bootlin License: Creative Commons Attribution - Share Alike 3.0 http://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/1 From Bootloader to user space - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/1 Kernel Bootstrap (1) How the kernel bootstraps itself appears in kernel building. Example on ARM (pxa cpu) in Linux 2.6.36: ..
    [Show full text]
  • Metal C Programming Guide and Reference
    z/OS Version 2 Release 3 Metal C Programming Guide and Reference IBM SC14-7313-30 Note Before using this information and the product it supports, read the information in “Notices” on page 159. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-02-15 © Copyright International Business Machines Corporation 1998, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents List of Figures...................................................................................................... vii List of Tables........................................................................................................ ix About this document.............................................................................................xi Who should read this document................................................................................................................. xi Where to find more information..................................................................................................................xi z/OS Basic Skills in IBM Knowledge Center.......................................................................................... xi How to read syntax diagrams......................................................................................................................xi How to send your comments to IBM......................................................................xv
    [Show full text]
  • Cluster Server Agent Developer's Guide
    Veritas™ Cluster Server Agent Developer’s Guide Windows 2000, Windows Server 2003 5.0 11293735 Veritas Cluster Server Agent Developer’s Guide Copyright © 2007 Symantec Corporation. All rights reserved. Veritas Cluster Server 5.0 Symantec, the Symantec logo, Storage Foundation, are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be “commercial computer software” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com Third-party legal notices Third-party software may be recommended, distributed, embedded, or bundled with this Symantec product. Such third-party software is licensed separately by its copyright holder.
    [Show full text]
  • Apache::Perlrun, and the Apache/Perl API
    Introduction and Incentives 1 Introduction and Incentives 1 Introduction and Incentives 15 Feb 2014 1 1.1 Description 1.1 Description An introduction to what mod_perl is all about, its different features, and some explanations of the C API, Apache::Registry, Apache::PerlRun, and the Apache/Perl API. 1.2 What is mod_perl? The Apache/Perl integration project brings together the full power of the Perl programming language and the Apache HTTP server. With mod_perl, it is possible to write Apache modules entirely in Perl, letting you easily do things (such as running sub-requests) that are more difficult or impossible in regular CGI programs. In addition, the persistent Perl interpreter embedded in the server saves the overhead of starting an external interpreter, i.e. the penalty of Perl start-up time. And not the least important feature is code caching, where modules and scripts are loaded and compiled only once, and for the rest of the server’s life they are served from the cache. Thus the server spends its time only running already loaded and compiled code, which is very fast. The primary advantages of mod_perl are power and speed. You have full access to the inner workings of the web server and can intervene at any stage of request processing. This allows for customized processing of (to name just a few of the phases) URI->filename translation, authentication, response generation, and logging. There is very little run-time overhead. In particular, it is not necessary to start a separate process, as is often done with web-server extensions.
    [Show full text]
  • HP Openvms MACRO Compiler Porting and User's Guide
    HP OpenVMS MACRO Compiler Porting and User’s Guide Order Number: AA–PV64E–TE January 2005 This manual describes how to port Macro-32 source code written for the VAX MACRO compiler to the MACRO compiler for OpenVMS running on either an HP OpenVMS Industry Standard 64 or HP OpenVMS Alpha system. It also describes how to use the compiler. Revision/Update Information: This revised manual supersedes the OpenVMS MACRO-32 Porting and User’s Guide for OpenVMS Version 7.3. Software Version: OpenVMS I64 Version 8.2 OpenVMS Alpha Version 8.2 Hewlett-Packard Company Palo Alto, California © Copyright 2005 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Printed in the US ZK5601 The HP OpenVMS documentation set is available on CD-ROM. This document was prepared using DECdocument, Version 3.3-1b. Contents Preface ............................................................ ix Part I Concepts and Methodology 1 Preparing to Port Macro-32 Code 1.1 Features of the MACRO Compiler ..............................
    [Show full text]