Week of 05/18/2008 - 02:00 to 05/25/2008 - 01:59
(Followup to part VII)
One of the most important things people need is a way to read Topic Map content from disk, and maybe write it back later. This is usually referred to as persistency, but the whole persistency business can be quite contrived. The Perl TM distribution tries to help to keep things organized.
When map content is stored in a text file, say in XTM 2.0 format, then we can do the following to connect this with an in-memory object:
- Thomas Klausner (aka domm)
- Perl 5.10 Intro + Neue Features
- Museumsquartier - MQ Electric Avenue - Quintessenz
- Jonathan Worthington: Rakudo Update
- Talk 'die Perl, die!'
in den Räumlichkeiten des NIG (Neues Institutsgebäude)
NIG, Raum D116, im Gang D
Another outworld-ish experience I had at Bond University was when attending examiner meetings.
I never really figured out what these meetings at the end of each teaching trimester were supposed to achieve. But neither did any of my colleagues. The meetings were held after all (centrally scheduled) exams and everyone happily showed up. So I did too.
What we did there - under the competent supervision of the dean of the day - is to look at every students' mark in every single course.
What we looked for were anomalies, such as a
I have just uploaded a new version of TM::Corpus onto CPAN.
One notable addition is TM::Corpus::MLDBM which allows to persistently store the document corpus on disk. That definitely helps as you would not want to download mega bytes over and over again. MLDBM is the acronym for multi-level DB and you probably know Berkeley DB files for years.
Maybe I will also add a DBI (read: relational) backend to TM::Corpus at some later time.
The other addition is that some functionality \