The Iterable concept is an extremely abstract way to treat a collection functionally, without worrying about indexers or iterators.

I've been working on an enhancement to Jini servce lookup in my reef project over on jini.org. I've still got more work to do before getting to the proposal stage. Here's where I'm at.

I've been an active user of Jini and Java for the life of these platforms. The distruption that Web Services is causing in the software industry is amazing. Is this an investment for good, or a cost that we'll wish we'd skipped?

There's one rather mind-bending idiom that appears periodically in Java generics. Here's what it looks like: class SelfBounded<T extends SelfBounded<T>>

As developers get more savvy in using small-grained requests and web browsers get more powerful as general-purpose processors, this atomization will enable higher-order layering of behavior into rich, value-added applications.

There are a lot of misconceptions about what Moore's Law actually says and even more confusion over what it implies. We're in the early phases of a major transition...

Ostream iterators are a handy but under-utilized tool for using the STL to output containers and ranges. Here I provide an alternative, which has a more pleasing syntax.

There appear to be some strange side effects on packages when using generics.

In the STL there exist numerous concepts such as Random Access Containers, and Back Insertion Sequences. Boost has introduced several improved Range concepts. I've got a new one for the list, the Iterable concept.

I'm hoping this is an obvious one and that my brain is just fried from over-generification.

I came across another generic puzzle and hope that someone has some insights.

I have come up with a first specification of OsXml, an XML schema for publishing and distributing Open-Source code.

Wouldn't it be nice if there existed a standard for XML when you don't need the whole thing? I propose a strict subset of XML called XML minus minus (XML--).

I set out to explore how the compiler treats a plain List vs. a List<?>, and in the process found something mysterious.

A concept is a description of a type, including functions signatures, preconditions, postconditions, invariants, and member types. In C++ it is an abstract idea, but in the next Heron it will exist as a construct. There is one small problem with the syntax when writing function signatures which use concepts.