Expand description
Tokenizing (lexing) the RPSL from plain text to the Ast
abstract syntax tree.
Re-exports§
pub use ast::Ast;pub use filter::Filter;pub use lines::expressions;pub use lines::io_wrapper_lines;pub use lines::lines_continued;pub use lines::rpsl_objects;pub use lines::RPSLObject;pub use lines::RpslExpr;pub use mp_import::Casts;pub use mp_import::Entry;pub use mp_import::PeeringAction;pub use mp_import::Versions;pub use peering::AsExpr;pub use peering::ComplexAsExpr;pub use peering::Peering;pub use rpsl_object::AsOrRouteSet;pub use rpsl_object::AutNum;pub use rpsl_object::FilterSet;pub use rpsl_object::PeeringSet;
Modules§
- ast
- filter
- lines
An RPSL object is textually represented as a list of attribute-value pairs. Each attribute-value pair is written on a separate line. The attribute name starts at column 0, followed by character “:” and followed by the value of the attribute. The attribute which has the same name as the object’s class should be specified first. The object’s representation ends when a blank line is encountered. An attribute’s value can be split over multiple lines, by having a space, a tab or a plus (‘+’) character as the first character of the continuation lines. The character “+” for line continuation allows attribute values to contain blank lines. More spaces may optionally be used after the continuation character to increase readability. The order of attribute-value pairs is significant.
- mp_
import - peering
- rpsl_
object