There are a few things to note: not anything that fits into a record fits into a class and viceversa. So, you will need to carefully think on what types you will be using to corelate the 2.
In any case, you can use an integer type for reading a string type. There are no limits, the whole idea is that you must be carefull on how you do it.
The current demo only supports all integer types and string types (obviously only string types that fit in a record, and from those, only the ASCII ones).
As you can see, the design of the demo allow you to write your own readers and writers, plus the main converter is event driven in case you need to do some other processing. As in this demo, adding a CRLF after each record and properly adding a comma between the records.
You will use the convertField event to do any necessary conversions (like string formating, special float or date conversions, etc).
You can also use this to directly convert from and to binary data representation on network streams and thus implementing a nice binary network serialization.
Just as easy you can use this to make an XML serialization/deserialization engine.
This demo was designed to be generic (even thought it can still be made more generic) so that it can be used as a root for most needed application types.

NOTE: The order of the fields in the record MUST match the order of the PUBLISHED properties in the stub class

Source Code