Parent

Class Index [+]

Quicksearch

Mail::StructuredField

Provides access to a structured header field

Per RFC 2822:

 2.2.2. Structured Header Field Bodies
 
    Some field bodies in this standard have specific syntactical
    structure more restrictive than the unstructured field bodies
    described above. These are referred to as "structured" field bodies.
    Structured field bodies are sequences of specific lexical tokens as
    described in sections 3 and 4 of this standard.  Many of these tokens
    are allowed (according to their syntax) to be introduced or end with
    comments (as described in section 3.2.3) as well as the space (SP,
    ASCII value 32) and horizontal tab (HTAB, ASCII value 9) characters
    (together known as the white space characters, WSP), and those WSP
    characters are subject to header "folding" and "unfolding" as
    described in section 2.2.3.  Semantic analysis of structured field
    bodies is given along with their syntax.

Public Class Methods

new(name = nil, value = nil, charset = nil) click to toggle source
    # File lib/mail/fields/structured_field.rb, line 27
27:     def initialize(name = nil, value = nil, charset = nil)
28:       self.name    = name
29:       self.value   = value
30:       self.charset = charset
31:       self
32:     end

Public Instance Methods

charset() click to toggle source
    # File lib/mail/fields/structured_field.rb, line 34
34:     def charset
35:       @charset
36:     end
charset=(val) click to toggle source
    # File lib/mail/fields/structured_field.rb, line 38
38:     def charset=(val)
39:       @charset = val
40:     end
default() click to toggle source
    # File lib/mail/fields/structured_field.rb, line 42
42:     def default
43:       decoded
44:     end
errors() click to toggle source
    # File lib/mail/fields/structured_field.rb, line 46
46:     def errors
47:       []
48:     end

Disabled; run with --debug to generate this.

[Validate]

Generated with the Darkfish Rdoc Generator 1.1.6.