Older blog entries for maelstorm (starting at number 6)


Suffering greatly. Trying to get my house ready for market, so I spent the weekend cleaning it. Apparently, we stirred up enough dust to trigger a rather severe allergy attack, so I'm looped out today, and mostly useless.


Looks like I've got three projects that are going to be dumped on me simutaniously. Not necessarily looking forward to that. I'm also in the process of procuring an expidited passport, because they need me to fly to London to provide technical assistance for the final handoff of the project that I've been managing. Should be fun.
Looks like colin has managed to fix our python support to something approaching usefulness. Variable bindings are preserved, and we can handle a few of the base python classes. opiate is working on extending the support to user defined classes right now, but is bottlenecked by some of the code that I'm working on that represents Objects with member variables/functions. Should be interesting.
13 Apr 2001 (updated 13 Apr 2001 at 18:18 UTC) »

Project status

Looks like I'm going to get a little time to work on coldstore during the weekend. If nothing else, I'm going to have to review opiate's work, because his Python binding to the store is finally working for initial population of the store, but not for subsiquent loads of the store.


Blah. Finishing up the last of some reports for site usage for out of our clients websites. I hate writing reports. It did get me to do some nice refactoring, though, to clean up our reporting class library. Changed the Report generation class to an interface, instead of being solely for PDF based reports. Modified some other stuff to make it not rely on absolute file paths, but rather the class path (with the absolute path as a fallback if the resource load fails).

It sounds like we're going to get some more time to pull a better class library out of the codebase after we do our last bits of wrap-up. Which is good. I hate having to re- invent the wheel. Maybe I can convince them to use tapestry for the next project, though it looks like we're going pretty purely over to XSLT and XML for our next projects.

11 Apr 2001 (updated 11 Apr 2001 at 14:01 UTC) »

bruce: What are you guys doing with Cubik? I thought TOM had become abandonware...

neale: Yes, colin worked on coldmud a long time ago. We still have some of the old sources lying about, as well as a couple of experimental cores. You wouldn't happen to be the same neale who was on the cold dark/genesis mud?

Coldstore was seeded by Colin's desire to have something that would work very well as a testbed for experimenting with both document storage and the collaboration that we've grown to love on various user programmable muds. But I suppose that's what most of the newer text based muds are for these days.

The developers of coldstore tend to hang out on Xao MOO, whose primary focus has become talking about development of coldstore, and various interesting bits of political and philosophical rhetoric and debate. Please stop by. It's a fun time, and an excellent place to get real time feedback if you're stuck on a programming problem at your $job. Or even if you're not.

10 Apr 2001 (updated 10 Apr 2001 at 18:15 UTC) »

nzkoz: Try compiling with -Weffc++ if you use gcc as your compiler -- it provides warnings during compile time for code patterns that are thought to be bad in the text of Effective C++

<Gripes/Feature requests for Advogato>

There seems there are a few parts of the process of community building that Advogato has missed in its attempt to foster a strong community of developers. First, it seems that despite an observer level user being able to create a project, there's no way for another observer working on that project to note that they are, indeed, part of their project. Because of that, the project I'm working on, Coldstore, now has two project pages: here and here.

I suppose part of it is case insensitivity in project names, which is ok. But the other issue is that we can't add each other to the same project.

Second issue: When users certify you, it would help if they could attach a comment that was reviewable by the user for why they chose the level of qualification of the user. Why? Since we're trying to build a community of qualified peers that can help us with well envisioned and rational critism for our ideas, it would be helpful for those who are deemed only observers or apprentices to know what our peers think needs to be improved.

</Gripes/Feature requests for Advogato>

Peeve of the day: Java doesn't provide an easy way (or even a one off) of introspecting into any publicly exported classes to find out whats there at runtime.

I suppose the reason for this is that it might be seen as a potential security violation. After all, your program should know exactly what it's dealing with.

The task I wanted to accomplish was the automatic detection of all implementers of a certain interface for report generation at runtime in order to build a composite report and another for finding all batchable tasks in the jar. There are other, more specific ways of doing this, that also require more code management -- I could add a static set of calls in the class declaration of the various implimentors that automaticly registered the class with some singleton management class. I could use a property file with a list of class names of reports that I wanted to generate (or tasks that I wanted to have run). It was suggested that if I knew the jar file name, I could also suck out the class names from the Manifest (haven't looked into that option yet).

Any other suggestions?

31 Jan 2001 (updated 7 Feb 2001 at 16:50 UTC) »

Spent my evening after work playing with Coldstore's Chaos language. While it already works, it's all direct interpretation, and only minimal error checking for stack depth requirements. So I spent the evening extending the primatives list to include stack information.

Next will be some decisions on how to do bytecode representation, and a seperate version of the lexer that emits the bytecode, rather then direct interpretation.

Looked at a RPN based functional language called Joy -- there's definitely some interesting concepts that could be borrowed from it, and it's one of the reasons for adding the stack effects notation to the current set of primative operations. I think in a later iteration, I'll try to use that to guess 'correctness' of procedures and stacks.

And spotted a scary thing on comp.lang.functional: Scheme implemented in JavaScript.

I've been spending the past few weeks trying to understand functional programming, especially OCaml. From what I've read, it's supposed to be one of the fastest functional programming language implementations (and corrispondingly, one of the fastest ML implementations) out there.

It took a few years for it to start to crystalize for me. I think I first started looking at SML around 1996, and tried to convince, without success, one of my Math/Com Sci instructors to assist me in a independent study exploration of it. His reasoning was that: 'At this point in your degree, you should be able to pick up any programming language'.

I guess the only thing he really didn't count on is that ML requires a different mindset then the imperitive programming languages that were pretty much the standard. I had taken some LISP with him, but the approach there was limited to symbolic manipulation for simple AI stuff, like eliza, deeply recursive functions, and information space searching.

Thats all well and good, but it still didn't prepare me for actually having to worry about domain mapping, and something so well and thoroughly steeped in the lambda calculus, and side effect free coding.

But it's finally making sense. I kinda wish I had a project to use it on.

The big reason I'm looking into functional programming right now is that I'm hoping to figure out some of the nifty implicit typing rules for Coldstore's second programming language, freon.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!