I've recently been toying with the idea of ephemeral classes. An ephemeral class is a class which does not have attributes. The immediate benefits of such classes is that their features can be used for objectless calls, the same way we can access constants or external features.
Last week I was at the LASER 2009 summer school on Software Testing. It was pretty interesting and one brief talk captured my attention. The speaker, Martin Nordio, asked the audience if they knew Eiffel and only a few hands were raised. So he asked if they knew Java instead. Everyone raised his hand.
I was lucky to get my hands on an iPod Touch. The first thing I did was to install SSH, gcc, subversion, vim, gdb et voila! Checked out the source of the Eiffel Software runtime. Tonight, I'll compile the runtime and run our regression test suite on it to make sure everything works properly.
When this is done, I'll look at how to use Eiffel for iPhone/iPod Touch development.
Mac fanatics out there might have heard that there is native implementation of GTK running on MacOSX. There's been a bit of backlash against the port because it doesn't provide a native MacOSX look and feel, but we are assured that they are working on it.
Last week, I was wrapping some C++ code for a customer and I was surprised that my code did not work properly. I'm not a C++ programmer and thus this error might have been a typical gotcha but still this was a very surprising behavior.
A project I started a few years ago (I could say completed but I got bored) I've recently revisited and just updated to use newer Eiffel syntax. It concerned itself with something not too often published uses for Eiffel, an API stack whose bottom layer interacts with low level system calls to manipulate hardware.