I cannot make heads or tails of the ATA standards. More specifically, I cannot find the information from tutorials and example code in the standards themselves (ie, the draft versions from t13.org).
On a more general note, I'm trying to understand the various official documentation out there instead of relying on example/tutorial code. I want to learn how to "read documentation" which is odd but seems to be a good skill to have especially since it appears to require too much effort to get people to write easy-to-understand documentation.
ATA Docs
-
GuiltySpark
- Posts: 7
- Joined: Sun Dec 16, 2007 9:47 am
- Location: The (Other) Counterweight Continent
ATA Docs
"Pissing people off since 1986."
"Edible: n, As in a worm to a toad, a toad to a snake, a snake to a pig, a pig to a man, and a man to a worm."
"Edible: n, As in a worm to a toad, a toad to a snake, a snake to a pig, a pig to a man, and a man to a worm."
Most of those documentations that you are referring to are Technical Documentations or documents. I had a lot of problems reading ATA documentations also. What helped me understand those documentations better was getting my hands dirty with the actual coding process. When you are merely reading a document, you don't know what to expect from it. Once you start writing a program and you get stuck, you know exactly what you are looking for in the document. That's when it starts to make sense.
On the field with sword and shield amidst the din of dying of men's wails. War is waged and the battle will rage until only the righteous prevails.