Code Structs
API ./. Framework(ed)
Perl and inline code expansion (internal generation) and the meta-design. Use of configs for every kind of component is such a weird thing, that it was impossible not to decide to give it a try. E.g. to work with Manifest files, defining each and every main-variable (eventually type, Perl does not predefine a variables type usually), for any module applicable. Preprocessing of INI files, towards a compact set of classes, but for everything left and right off the road. From the beginning of bootstrapping, putting on the walk along equipment for shoemakers business, it would have been nothing but crazy not taking the system's ENVironment plugin to go booster. There are the variables, values or paths; the latter just a separated list by colons well done. Come byways":" Templates, useful for quickly setting up proof-of-concept programming. For text or hypertext anyway, but for generating markup, XML-DB early version still is filebased only, templates ease so much more.
XSL. Generation into source script tree triggered more of API mind. Great stuff, however poorly documented - maybe for reason by the designers - nor architects.
Java. Recent introductions extending the language, inspired by C plus plus mechanics towards preprocessor antes compilaje, close to big crap. Too much of unfinitive, generics and annotations by far enough of too few, for having closelined leasing rewards. Not only 'unthought' of the concept kind inside the lang struct, harder than worse, too much of never done! Loops besides, like in others, see perl, python e.g. And more to come for unawaited. However backdays light a bit of signing decry|ap(t). For CPI: yes. Workbench shellgineering? Yes too, lot more, for package resucked, and yet'll do: rest done in next sect[s].
Regular Expressions. There's the chaos inside. Order-sorting? Impossible now, later for sure.
Bash. Environment plugin point checks layers sys-licks. A guitar on it's own, crying like Peter!
All? Not by now.
Perl and inline code expansion (internal generation) and the meta-design. Use of configs for every kind of component is such a weird thing, that it was impossible not to decide to give it a try. E.g. to work with Manifest files, defining each and every main-variable (eventually type, Perl does not predefine a variables type usually), for any module applicable. Preprocessing of INI files, towards a compact set of classes, but for everything left and right off the road. From the beginning of bootstrapping, putting on the walk along equipment for shoemakers business, it would have been nothing but crazy not taking the system's ENVironment plugin to go booster. There are the variables, values or paths; the latter just a separated list by colons well done. Come byways":" Templates, useful for quickly setting up proof-of-concept programming. For text or hypertext anyway, but for generating markup, XML-DB early version still is filebased only, templates ease so much more.
XSL. Generation into source script tree triggered more of API mind. Great stuff, however poorly documented - maybe for reason by the designers - nor architects.
Java. Recent introductions extending the language, inspired by C plus plus mechanics towards preprocessor antes compilaje, close to big crap. Too much of unfinitive, generics and annotations by far enough of too few, for having closelined leasing rewards. Not only 'unthought' of the concept kind inside the lang struct, harder than worse, too much of never done! Loops besides, like in others, see perl, python e.g. And more to come for unawaited. However backdays light a bit of signing decry|ap(t). For CPI: yes. Workbench shellgineering? Yes too, lot more, for package resucked, and yet'll do: rest done in next sect[s].
Regular Expressions. There's the chaos inside. Order-sorting? Impossible now, later for sure.
Bash. Environment plugin point checks layers sys-licks. A guitar on it's own, crying like Peter!
All? Not by now.
bnw - 2013/01/24 12:05 - last edited: 2013/01/21 10:59
Trackback URL:
https://bnw.twoday.net/stories/admin-codestructs/modTrackback