Re: The trouble with awesome
On Wed, May 30, 2012 at 6:00 AM, Moritz Lenz wrote: > > I'd still start with simple script files, because that's what most > programmers are most familiar with. > I'd do them in Huffman order; the interpreter involves the least typing to start, and it's useful for demonstrating concepts. Usually, an abstract principle needs some specific examples to clarify it. > Where would you put nested data structures and custom classes? Assuming you're talking about things like arrays of arrays, I'd put them between structured and unstructured data. A simple table of results by month can get into that sort of structure. Custom classes are definitely around the "higher order".
[perl6/specs] f29d4c: [S32::Exception] general policy for what data to c...
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: f29d4ced93a2bae8fcd6a7c9d4fedc665040f3a5 https://github.com/perl6/specs/commit/f29d4ced93a2bae8fcd6a7c9d4fedc665040f3a5 Author: Moritz Lenz Date: 2012-06-03 (Sun, 03 Jun 2012) Changed paths: M S32-setting-library/Exception.pod Log Message: --- [S32::Exception] general policy for what data to carry around Commit: d88cbf4074ed84100f1e87492636a20ec732ea55 https://github.com/perl6/specs/commit/d88cbf4074ed84100f1e87492636a20ec732ea55 Author: Moritz Lenz Date: 2012-06-03 (Sun, 03 Jun 2012) Changed paths: M S32-setting-library/Exception.pod Log Message: --- X::IO does X::OS Commit: 64947f6fbd87a7a793127f673377785ea988deb6 https://github.com/perl6/specs/commit/64947f6fbd87a7a793127f673377785ea988deb6 Author: Moritz Lenz Date: 2012-06-03 (Sun, 03 Jun 2012) Changed paths: M S32-setting-library/Exception.pod Log Message: --- note about mixing in X::Comp Compare: https://github.com/perl6/specs/compare/8f29a46...64947f6
