nklein software

When I wrote the method-versions library, I had read about ContextL and decided that I only wanted a very small subset of it and wanted it to be very easy to use. It turns out that I didn’t quite understand the complexity-level of ContextL. It is actually very similar to what I had wanted.

With my library, you set up some versions and a variable to track the current version:

In ContextL, you just set up some layers:

In my library, you then set up a generic function that uses a special method combination that keys off of the special variable:

In ContextL, you declare a layered function:

In my library, you then declare different methods using the version as a method qualifier.

In ContextL, you declare layered methods specifying which layer the functions belong to:

In my library, you set your special variable appropriately and invoke the method:

In ContextL, you declare which layer you want to be active when you go to invoke the method:

My library does not let you specify other method qualifiers like :around or :after. ContextL does.

I am going to leave my library published because I think it is a reasonably understandable, yet non-trivial, use of non-standard method combinations. However, I am going to end up using ContextL for the projects that I had intended for my library.