Bug 102712 - [NEW PORT] devel/libyaml: A YAML 1.1 parser and emitter written in C
Summary: [NEW PORT] devel/libyaml: A YAML 1.1 parser and emitter written in C
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Pav Lucistnik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-31 02:30 UTC by Ying-Chieh Liao
Modified: 2006-09-01 10:51 UTC (History)
0 users

See Also:


Attachments
libyaml-0.0.1.shar (3.90 KB, text/plain)
2006-08-31 02:30 UTC, Ying-Chieh Liao
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ying-Chieh Liao 2006-08-31 02:30:21 UTC
LibYAML is a YAML 1.1 parser and emitter written in C.

LibYAML covers presenting and parsing processes. Thus LibYAML defines the
following two processors:
   * Parser, which takes an input stream of bytes and produces a sequence
     of parsing events.
   * Emitter, which takes a sequence of events and produces a stream of
     bytes. 

The processes of parsing and presenting are inverse to each other. Any
sequence of events produced by parsing a well-formed YAML document should
be acceptable by the Emitter, which should produce an equivalent document.
Similarly, any document produced by emitting a sequence of events should
be acceptable for the Parser, which should produce an equivalent sequence
of events.

The job of resolving implicit tags, composing and serializing representation
trees, as well as constructing and representing native objects is left to
applications and bindings. Although some of these processes may be covered
in the latter releases, they are not in the scope of the initial release of
LibYAML.

WWW: http://pyyaml.org/wiki/LibYAML

Generated with FreeBSD Port Tools 0.77
Comment 1 Pav Lucistnik freebsd_committer freebsd_triage 2006-08-31 19:43:32 UTC
State Changed
From-To: open->feedback

We do not accept new unmaintained ports. Are you willing to maintain this port? 


Comment 2 Pav Lucistnik freebsd_committer freebsd_triage 2006-08-31 19:43:32 UTC
Responsible Changed
From-To: freebsd-ports-bugs->pav

Track
Comment 3 Ying-Chieh Liao freebsd_committer freebsd_triage 2006-09-01 10:50:30 UTC
State Changed
From-To: feedback->closed

committed