Nice post. I've learnt too many of these the hard way
with inherited formats. In particular, one format lacked
easily identifiable record types so the a record's
subtype may depend on the first field or the first and
second, the length of the second depending on the first...
Other thoughts:
- Dependency ordered records, that is parents before
their children.
- Count, checksum or hash at the end (I think a
line count gives a false sense of protection from
corruption).
- The two points above make file processing more streamable.
- Consider specifying character encodings.
- Don't be cryptic to save characters, have a plain
text format and zip it.
See also the Art of Unix Programming
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|