Question

为什么使用pple号档案?

视窗使用基文档,这种文件可能不太灵活,但空间也较少,因为同样的原因,联合起来的空间低于XML。

They could even use JSON for their configuration, it s at least as easy to parse, supports the value types they need (dict etc.) and takes up the least space.

Answer 1

The original property list Format found in NeXTSTEP look a Much such as JSON, but with small different syntax. 当NeXTSTEP成为麦克风第十,这一格式被你今天看到的XML版本所取代。新的格式比你能够理解的旧格式稍有改进。

财产清单可以包含若干数据类型,JSON(和INI文档)不能:被指定为真实数字(点)或分类、日期和基64编码的双元数据。此外,JSON的t

MacOS 10.2和新版本包括一种比XML更具有空间效益的双双位清单格式,而列入清单的文档可在两者之间无损地转换。

Answer 2

由于NeXTSTEP使用这些产品,因此 Apple果也采用这些产品。

。财产清单:

Under NeXTSTEP, property lists were designed to be human-readable and edited by hand, serialized to ASCII in a syntax somewhat like a programming language.

NeXTSTEP used one format to represent a property list, and the subsequent GNUstep and Mac OS X frameworks introduced differing formats.

While Mac OS X can also read the NeXTSTEP format, Apple sets it aside in favor of two new formats of its own.

In Mac OS X 10.0, the NeXTSTEP format was deprecated, and a new XML format was introduced, with a public DTD defined by Apple. The XML format supports non-ASCII characters and storing NSValue objects (which, unlike GNUstep s ASCII property list format, Apple s ASCII property list format does not support). Since XML files, however, are not the most space-efficient means of storage, Mac OS X 10.2 introduced a new format where property list files are stored as binary files. Starting with Mac OS X 10.4, this is the default format for preference files.

Answer 3

我认为,这是从NeXTSTEP天遗留下来的一件事。

友情链接