X/Open Curses Issue 7技术标准参考

unix

Curses

5星 · 超过95%的资源需积分: 5 105 浏览量更新于2024-07-31 3 收藏 1.02MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"Curses库参考手册是一份关于X/Open Curses标准的技术文档，主要针对Unix/Linux平台。这份手册由The Open Group在2009年发布，包含了Curses库的详细信息，包括新引入的功能、撤回的功能以及基础和增强的Curses库的符合性要求。手册中的内容涵盖了一系列术语和格式规范，旨在为开发者提供全面的Curses库使用指导。" Curses库是一个用于文本终端编程的API，尤其适用于Unix和类Unix系统，它允许程序员创建交互式和基于文本的应用程序，具有窗口管理、颜色支持和键盘事件处理等功能。Curses库在低级别的终端控制上提供了高级接口，使得开发者可以更轻松地管理屏幕输出和用户输入，而无需关注底层的终端操作细节。在标题和描述中提到的《Unix/Linux下的Curses库开发指南》可能是对Curses库的一个介绍性书籍，但完整的资源可能难以找到，因此这份X/Open Curses的官方手册成为了学习和参考的重要资源。在手册的章节1.1中，介绍了文档本身的特点及其与先前版本的关系。其中，1.1.1部分讲述了此文档如何与之前的版本相对应，1.1.2和1.1.3分别阐述了第七期版本中新增和撤销的功能，而1.1.4则提及了第四期版本引入的特性。这些信息对于了解Curses库的发展历程和当前版本的更新至关重要。 1.2章节关于符合性，分为1.2.1基础Curses符合性和1.2.2增强Curses符合性，这部分详细列出了应用程序如何实现对Curses库的兼容，以及遵循哪些规范来确保跨终端的一致性。 1.3章节涉及术语，1.3.1部分特别提到了阴影文字，这可能是指手册中用来区分不同性质或重要性的文本标记方式。理解这些术语对于准确理解和使用Curses库至关重要。 1.4章节讨论了文档的格式，这通常包括如何组织信息、使用代码示例、注释和警告等内容，有助于读者更有效地阅读和理解手册。这份X/Open Curses的参考手册为开发者提供了关于Curses库的权威指南，涵盖了从基本概念到具体实现的广泛内容，是开发基于文本终端应用的必备参考资料。通过深入学习，开发者可以利用Curses库构建高效、用户友好的命令行界面，提升终端用户体验。

资源详情

资源推荐

This Document Introduction

1.1.2 Features Introduced in Issue 7

The following features areintroduced in Issue 7:

• Function prototypes areupdated to use const whereappropriate.

• The tiparm() function is added.

• The following new utilities areadded in Chapter 6:

infocmp

tic

tput

untic

1.1.3 Features Withdrawn in Issue 7

The following interfaces arewithdrawn in this document:

Withdrawn Interfaces

tgetent()

tgetﬂag()

tgetnum()

tgetstr()

tgoto()

vwscanw()

vwprintw()

1.1.4 Features Introduced in Issue 4

The following features wereintroduced in Issue 4.

Internationalization

This version of the Curses speciﬁcation has been enhanced to support a wide range of

internationalized capabilities. Traditional single-byte character operations arepreserved, and

multi-byte and wide-character interfaces areincluded to allow use of the Curses features with a

wide range of character codesets. The actual codesets supported areimplementation-deﬁned.

Enhanced Character Sets

Emerging character set standards specify characters with a constant width greater than an octet

(such as ISO/IEC 10646-1: 1993), or multi-byte codesets (such as the ISO 2022: 1986 EUC

encoding used to encode the Japanese and Chinese language characters).

The previous version of the Curses speciﬁcation was capable of supporting ISO 8859-1: 1987.

Many traditional implementations only supported ISO/IEC 646: 1991 and preceding codeset

speciﬁcations, in which the length of a character was an octet.

The primary standardization issue with the increasing size of a character is that neither the ANS

X3.159-1989 or ISO/IEC 9899: 1990 C language deﬁnition requires the existence of an integral

data type greater than 32-bits. Although such data types arecommonly deﬁned, The Open

Group cannot requiresupport for them at this time. The opaque data type cchar_t and

associated routines address this issue.

2 Technical Standard 2009

Introduction This Document

Writing Direction

The references to writing direction have been generalized to permit both right-to-left and left-to-

right writing. This document does not specify whether the implementation supports morethan

one direction of writing. The behavior of the interfaces in this document is unspeciﬁed if the

writing direction is vertical, or if the writing direction is horizontal with row height greater than

one.

Wide and Non-spacing Characters

New interfaces areintroduced for use with wide characters and wide-character strings. The

traditional single-byte character string interfaces have been made moregeneral for use with

multi-byte character strings. The traditional chtype interfaces note that they areusable only in

restricted environments and do not support extensible attributes. The behavior of the chtype

interfaces in this document is unspeciﬁed if the char data type is greater than 8 bits, or if any

single byte character takes morethan one display column, or if the application or

implementation stores a multi-byte or wide-character value into a chtype object.

Anew,extensible attribute model has been provided for wide-character interfaces. The display

model has been generalized to support both multi-column characters and non-spacing

characters. The concept of a complex character is introduced.

Other Enhancements

New interfaces and capabilities areintroduced to support color terminals, printers, modems,

and mice.

1.2 Conformance

An implementation conforming to this document shall meet the requirements speciﬁed by Base

Curses conformance (see Section 1.2.1)orbyEnhanced Curses conformance (see Section 1.2.2,

on page 4).

1.2.1 Base Curses Conformance

An implementation that claims Base Curses conformance shall meet the following criteria:

• The system shall support all the interfaces and headers deﬁned within this document

except that it need not support those occurring on reference pages labeled ENHANCED

CURSES and in shaded areas marked with the EC margin legend.

• The chtype data type shall support at least octet-based codesets, such as ISO 8859-1: 1987.

• The system may provide additional or enhanced interfaces, headers, and facilities not

required by this documen, provided that such additions or enhancements do not affect the

behavior of an application that requires only the facilities described in this document.

X/Open Curses, Issue 7 3

Conformance Introduction

1.2.2 Enhanced Curses Conformance

An implementation that claims Enhanced Curses conformance shall meet the following criteria:

• The system shall support Base Curses conformance as deﬁned above.

• The system shall support the requirements in this document occurring on reference pages

labeled ENHANCED CURSES and in shaded areas marked with the EC margin legend.

• The system may provide additional or enhanced interfaces, headers, and facilities not

required by this document, provided that such additions or enhancements do not affect the

behavior of an application that requires only the facilities described in this document.

1.3 Terminology

The following terms areused in this document:

can

Describes a permissible optional featureorbehavior available to the user or application. The

featureorbehavior is mandatory for an implementation that conforms to this document. An

application can rely on the existence of the featureorbehavior.

implementation-deﬁned

Describes a value or behavior that is not deﬁned by this document but is selected by an

implementor.The value or behavior may vary among implementations that conform to this

document. An application should not rely on the existence of the value or behavior.An

application that relies on such a value or behavior cannot be assured to be portable across

conforming implementations.

The implementor shall document such a value or behavior so that it can be used correctly

by an application.

legacy

Describes a featureorbehavior that is being retained for compatibility with older

applications, but which has limitations which make it inappropriate for developing portable

applications. New applications should use alternative means of obtaining equivalent

functionality.

may

Describes a featureorbehavior that is optional for an implementation that conforms to this

document. An application should not rely on the existence of the featureorbehavior.An

application that relies on such a featureorbehavior cannot be assured to be portable across

conforming implementations.

To avoid ambiguity,the opposite of may is expressed as need not,instead of may not.

must

Describes a featureorbehavior that is mandatory for an application or user.An

implementation that conforms to this document shall support this featureorbehavior.

shall

Describes a featureorbehavior that is mandatory for an implementation that conforms to

this document. An application can rely on the existence of the featureorbehavior.

should

For an implementation that conforms to this document, describes a featureorbehavior that

is recommended but not mandatory.Anapplication should not rely on the existence of the

4 Technical Standard 2009

Introduction Terminology

featureorbehavior.Anapplication that relies on such a featureorbehavior cannot be

assured to be portable across conforming implementations.

For an application, describes a featureorbehavior that is recommended programming

practice for optimum portability.

undeﬁned

Describes the natureofavalue or behavior not deﬁned by this document which results

from use of an invalid program construct or invalid data input.

The value or behavior may vary among implementations that conform to this document.

An application should not rely on the existence or validity of the value or behavior.An

application that relies on any particular value or behavior cannot be assured to be portable

across conforming implementations.

unspeciﬁed

Describes the natureofavalue or behavior not speciﬁed by this document which results

from use of a valid program construct or valid data input.

The value or behavior may vary among implementations that conform to this document.

An application should not rely on the existence or validity of the value or behavior.An

application that relies on any particular value or behavior cannot be assured to be portable

across conforming implementations.

will

Same meaning as shall; shall is the preferred term.

1.3.1 Shaded Te xt

Shaded text in this document is qualiﬁed by a code in the left margin. The codes and their

meanings areasfollows:

EC X/Open Enhanced Curses

The functionality described relates to interfaces included to provide enhanced capabilities for

applications originally written to be compiled on systems based on the UNIX operating system.

Therefore, the features described may not be present on systems that conform to XPG4 or to

earlier XPG releases. The relevant reference pages may provide additional or morespeciﬁc

portability warnings about use of the material.

If an entireSYNOPSIS section is shaded and marked EC, all the functionality described on that

reference page is an extension.

The functionality on reference pages labeled ENHANCED CURSES and the functionality

ﬂagged with the EC margin legend areavailable only in cases wherethe _XOPEN_CURSES

version test macroisdeﬁned.

OB Obsolescent

The functionality described may be removed in a futureversion of this document. Applications

should not use obsolescent features.

Whereapplicable, the material is identiﬁed by use of the OB margin legend.

X/Open Curses, Issue 7 5

Format of Entries Introduction

1.4 Format of Entries

The entries in Chapter 4 and Chapter 5 arebased on a common format, as follows. The only

sections relating to conformance arethe SYNOPSIS, DESCRIPTION, RETURN VALUE, and

ERRORS sections.

NAME

This section gives the name or names of the entry and brieﬂy states its purpose.

SYNOPSIS

This section summarizes the use of the entry being described. If it is necessary to

include a header to use this interface, the names of such headers areshown; for

example:

#include <stdio.h>

DESCRIPTION

This section describes the functionality of the interface or header.

RETURN VALUE

This section indicates the possible return values, if any.

If the implementation can detect errors, ‘‘successful completion’’means that no error

has been detected during execution of the function. If the implementation does detect

an error,the error is indicated.

For functions wherenoerrors aredeﬁned, ‘‘successful completion’’means that if the

implementation checks for errors, no error has been detected. If the implementation

can detect errors, and an error is detected, the indicated return value will be returned

and errno may be set.

ERRORS

This section gives the symbolic names of the error values returned by a function or

stored into a variable accessed through the symbol errno if an error occurs.

‘‘No errors aredeﬁned’’means that error values returned by a function or stored into a

variable accessed through the symbol errno,ifany,depend on the implementation.

EXAMPLES

This section is informative.

This section gives examples of usage, whereappropriate.

APPLICATION USAGE

This section is informative.

This section gives warnings and advice to application developers about the entry.

RATIONALE

This section is informative.

This section contains historical information concerning the contents of the entry and

why features wereincluded or discarded by the developers of this document.

FUTURE DIRECTIONS

This section is informative.

This section provides comments which should be used as a guide to current thinking;

thereisnot necessarily a commitment to adopt these futuredirections.

6 Technical Standard 2009

剩余419页未读，继续阅读

醉梦书生

粉丝: 7
资源: 32

X/Open Curses Issue 7技术标准参考

curses头文件

NCURSES中文教程PDF

UNIX Linux下curses库开发指南

curses库怎么安装

手动编译安装curses库

基于curses库c++rpg文字游戏

python的curses库怎么安装

Linux中curses 库中box

curses库写自动换行

python curses库怎么安装

No module named '_curses'

pycharm怎么安装curses

curses.wrapper(main)作用

装了curses,仍报错ModuleNotFoundError: No module named _curses

no module named _curses

curses.h的安装和使用

Ubuntu获取curses

``` curses.wrapper(main)```解释代码

按照rabbitmq的时候报curses library not found 应该怎么解决

no module named '_curses'

最新资源