On 2010-04-21, at 04:00 , Faré wrote:
[...]
the additions to the code base over the past few months were devoted to two areas:
- configuration
- output translations
i neglect, for the moment, the configuration component of the asdf evolution and concentrate on questions related to output translations. even though the configuration mechanism contributes settings which affected the latter, they are in sufficiently independent, that an isolated analysis is reasonable.
Well, most of the translation code *IS* the configuration system. The output-files :around method itself is small, and its helpers are relatively simple,
the call graph[1] generator counted 66 functions. they appear to be split 1/3 - 2/3 between configuration and computation. that leaves about 44, which is about fifty percent of the pre 1.3 asdf function count.
except for the ugly directorize-pathname-host-device required for portability (that none of the previous solutions provided).
what requirement does that support? in particular, it would help to record in the manual section on "output translation implementation" why the process translates twice and what the respective realms mean.
--- [1] : reports.setf.de/asdf-calls-dot.pdf [2] : http://tinyurl.com/y6jv5mb