Lines Matching refs:reading

74 The YAML I/O library structures and simplifies reading and writing YAML 
89 there may be a normalization step, and when reading YAML there would be a
111 both reading and writing YAML. That is, the mapping between in-memory enum
190 single file.  That is why reading YAML produces a vector of your document type.
248 in sequence.  When reading, YAML I/O will validate that the string found
308 To support reading and writing of this enumeration, you can define a 
335 When reading YAML, if the string found does not match any of the strings
359 To support reading and writing of MyFlags, you specialize ScalarBitSetTraits<>
394 is done when reading and any unknown string values will result in a error. With 
418 To support reading and writing such fields, you need to use the maskedBitSet()
447 your specialization must create a temporary llvm::StringRef.  When reading,
493 and your specialization must convert that to your native data type when reading.
605 coordinates into polar when reading YAML.  
645 When reading YAML, the local variable "keys" will be a stack allocated instance
658 when reading YAML.  It never destroys the normalized object.  The denormalize()
694 When reading in a YAML document, the keys in the document can be in any order, 
700 This works for both reading and writing. For example:
716         // flags must come after cpu for this to work when reading yaml