Open System Services Porting Guide (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to Porting
- 2 The Development Environment
- 3 Useful Porting Tools
- 4 Interoperating Between User Environments
- Purpose of Interoperability
- The OSS User Environment
- OSS Commands for the Guardian User
- Guardian Commands for the UNIX User
- OSS Pathname and Guardian Filename Conversions
- Running the OSS Shell and Commands From TACL
- Running Guardian Commands From the OSS Shell
- Running OSS Processes With Guardian Attributes
- Using OSS Commands to Manage Guardian Objects
- 5 Interoperating Between Programming Environments
- 6 OSS Porting Considerations
- 7 Porting UNIX Applications to the OSS Environment
- 8 Migrating Guardian Applications to the OSS Environment
- General Migration Guidelines
- C Compiler Issues for Guardian Programs
- Using New and Extended Guardian Procedures
- Using OSS Functions in a Guardian Program
- Interoperating With OSS Programs
- Starting an OSS Program From the Guardian Environment
- C Compiler Considerations for OSS Programs
- Porting a Guardian Program to the OSS Environment
- How Arguments Are Passed to the C or C++ Program
- Differences in the Two Run-Time Environments
- Which Run-Time Routines Are Available
- Use of Common Run-Time Environment (CRE) Functions
- Replacing Guardian Procedure Calls With Equivalent OSS Functions
- Which IPC Mechanisms Can Be Used
- Interactions Between Guardian and OSS Functions
- 9 Porting From Specific UNIX Systems
- 10 Native Migration Overview
- 11 Porting or Migrating Sockets Applications
- 12 Porting Threaded Applications
- A Equivalent OSS and UNIX Commands for Guardian Users
- B Equivalent Guardian Commands for OSS and UNIX Users
- C Equivalent Inspect Debugging Commands for dbx Commands
- D Equivalent Native Inspect Debugging Commands for dbx Commands
- E Standard POSIX Threads Functions: Differences Between the Previous and Current Standards
- Glossary
- Index
The Development Environment
Open System Services Porting Guide—520573-006
2-17
Editing OSS Files
Editing OSS Files
The following subsections introduce the vi editor, which is available in the OSS
environment, and the emacs editor, which can be obtained for the OSS environment.
Editing OSS Files Using vi
For tasks such as writing memos and modifying C or C++ programs, editing text files is
one of the most common uses of any computer system. The vi text editor is
particularly well-suited for the day-to-day tasks of most computer users. Using vi, you
can quickly and easily open a file, edit it, and save the results. The vi editor operates
basically the same way on all UNIX based systems, so if you have used vi on a UNIX
system in the past, you should feel at home using it in the OSS environment.
While vi does not have some of the features of proprietary text editors and word
processors, it is a full-featured text editor with the following major features:
•
Fast processing, especially on start-up and global operations
•
Full-screen editing and scrolling capability (unlike the line editor ed, on which vi is
based)
•
Complex editing features such as global substitutions
For more information about the vi utility in the OSS environment refer to the vi(1)
online reference page, the Open System Services Shell and Utilities Reference
Manual, or the Open System Services User’s Guide.
Editing OSS Files Using emacs
Another editor available for the OSS environment is the emacs editor. This editor is not
automatically installed in the OSS environment. Check your system to see whether the
emacs editor is available.
The emacs editor is a customizable, extensible, real-time display editor. Online
documentation is provided with the emacs editor. Press Ctrl-H (Control key plus the H
or h key) to display your options. These options describe information needed to use the
emacs editor.
For more information about the emacs editor, refer to a commercial text.