Martin Zobel-Helas: Advantage of murphy being down
… it is quiet in my INBOX….
No Tags
Whilst downloading, installing and running Debian packages is easy, fun and “free”, most Web applications aren’t. I can’t be the only one that thinks there is a problem somewhere as for example, where are the all the Web applications listed on Freshmeat?
I have an idea for a Web application though I thought it would be cool to make it as Free software though it can be a pain.
Whilst downloading, installing and running Debian packages is easy, fun and “free”, most Web application services aren’t. I can’t be the only one that thinks there is a problem somewhere as for example, where are the all the free software Web services listed on Freshmeat?
I have an idea for a Web application though I thought it would be cool to make it as Free software though it can be a pain.
Likely<typename T> whose instances hold either a
return value of type T or an exception. A function that
can fail has a specialisation of this template as its return type.
The caller can check for failure if it knows how to handle it, or it
can ignore it - in which case the conversion to T or the
destructor will throw the exception. This is clever but doesn't seem
to be entirely satisfactory. The destructor which throws does first
check that no exception is already being processed, avoiding collision
of the two exceptions and consequent abrupt termination of the
program, but this can result in errors being unexpectedly ignored.
Introduction to Component-Level Testing, John Lakos
A marathon 3-hour talk on designing and testing software,
particularly C++ programs (the subject of his well-known
book) as a set of well-defined components.
Lakos first defined these components as being "physical" i.e. sets
of source files - normally a header file defining an interface, an
implementation file, and a test driver file. They may also include
metadata for the build system. He talked about the value of reusable
components (as if this wasn't obvious!) and the risk of introducing
circular dependencies - which essentially turn many components into
one and reduce reusability - if we fail to keep track of dependencies.
Software built out of components can be viewed as a hierarchy or stack
defined by dependencies. In a large system, components with similar
dependencies and dependents can be grouped together into packages or
package groups to simplify a view of these dependencies.
He explained that the test driver's dependencies count just as much
as the implementation's, because we cannot reasonably test a component
until we have tested its dependencies. Test drivers should also be
written to avoid depending on environmental settings and
configuration, so far as possible.
Finally, and perhaps most importantly, he spent a long time talking
about how to construct test cases and test data. I might try to
summarise this in a later entry if anyone's interested.
The Appliance of Science: Things in Computer Science that every
practitioner should know, Andrei Alexandrescu
Andrei began by complaining that OpenOffice Impress was even worse
than PowerPoint, but being able to use Linux (specifically Ubuntu)
more than made up for the pain.
He briefly presented four key ideas that he believes programmers
should understand and be ready to make use of:
const
std::initializer_list<T> & and when constructed with
this new form of initialiser they will receive this wrapper for a
constant array of element values. For types that do not, the values
in the list are treated as arguments to some other constructor, if one
matches. Otherwise, for compatibility, this may be treated as
aggregate initialisation.
C++ Standard Library report, Alisdair Meredith
There was far too much information here for me to even begin
to summarise. Suffice to say there are lots of good things coming
bu the library committee will have its work cut out to get them
all properly specified in time for the Committe Draft coming late
this year.

A couple of weeks ago my girlfriend buyed me a
Tom Tom Go 510
a very popular car GPS navigation system here in Spain (mostly because
goverment installed tons of radars for speed control).
Today, searching for some info to see if it was possible to update the device
using Linux, I discovered that the device
runs Linux! So, without knowing, I have an embbeded device running Linux, and
more than one million
people have also a device running Linux.
This clearly shows how Linux can be nice a solution for an embbeded commercial solution.
I should have known that taking a plane to Spain is risky. My
previous attempt: ... arriving in the airport, trying to be checked
in, being told that tickets have been cancelled, making calls,
being told that travel agency forgot to confirm a second time and
that new tickets have been booked for 2 days later, going home,
night before take off seeing that ticket to Spain has been
cancelled (ticket back still valid), going to the airport anyway,
being called that everything is ok, arriving at the airport, being
told that I have 2 tickets for the same flight...
Sorry to the people who expected me to be in Spain, I'm not
going to try my luck again tomorrow, though I'll try to be happy on
IRC
* debian/dbus.init
+ Add functionality to start/stop dbus dependent services based on their
LSB header.
Instead of installing an init script into /etc/dbus-1/event.d, services
depending on dbus should from now on install a regular sysv init script
and add an LSB header with "Required-Start: dbus".
So the dbus init script now adds a 'workaround' (likely, since this is done in
DBus, not in sysvinit) for the missing dependency handling in sysv-style init,
by taking care of the restarting itself. This is good, because init scripts
aren't distributed into two places anymore (soon).It probably highlights why we need to work on our init.
"(define a (call-with-input-file "friends.rss" read-xml))"seems to result in mzscheme (v352) holding 100Mb. What's with that? Anyway, now I've written a newitems function which extracts new items not listed in agg0i and old items which still appear in a blog and adds them to lists. Then, there's a function which tail-recurses over all the blog filenames, parsing the RSS, calling newitems on each one and building the lists of old and new items. Finally, agg1 is the new items appended to the old items. That is only calculated as it gets written out as a RSS file. I'll give it a few days of testing, then I'll publish a tarball. I use this to build my all.rss feed from my various source feeds, in case you didn't realise, as well as to run some planets for public and private use. Anyone got a suggestion how best to reduce the read-xml memory consumption? Upgrade? Switch dialect? I'd like some XML read/write functions and the SRFI list functions.
Next.