By convention, email signatures are commonly (somewhere) suggested to be no more than 4 lines in length. I wondered if it would be possible to hint at this whole scheme in just a few lines, e.g., as a way to gently slide the concept out into some forums.
Well, that's 5 lines, but it might actually work...
Note that here I've chosen to use the thinob tool to create the new object of the class. These are equivalent, except for error checking and such:
$ thinob foo.new MyClass
and
$ mkdir foo; ln -s ~/lib/thinob/MyClass foo/^
I'd also, confusingly perhaps, created the new foo object before defining the cpuinfo method -- maybe it would be better to finish the one before doing the other...
Except that with the class symlink in place, there's more direct (well, shorter) access to the class directory through the object, so:
By convention, email signatures are commonly (somewhere) suggested to be no more than 4 lines in length. I wondered if it would be possible to hint at this whole scheme in just a few lines, e.g., as a way to gently slide the concept out into some forums.
--
Ken Irving, my@ddress
$ mkdir foo; ln -s ~/lib/thinob/MyClassToDoStuff foo/^
$ thinob foo.do-something
http://www.thinobject.org
One problem of course, is that I have nothing there at thinobject.org, and I can't be promoting a non-existent link...
The idea here is to expose, or at least hint at, the major aspect of thinobject, that of providing a link to a directory of class methods.
Better might be to actually create and then call a method... can I do that in the room available??
--
Ken Irving, my@ddress
$ mkdir ~/lib/thinob/MyClass; thinob foo.new MyClass
$ echo cat /proc/cpuinfo > ~/lib/thinob/MyClass/cpuinfo
$ chmod +x ~/lib/tob/MyClass/cpuinfo; tob foo.cpuinfo
http://www.thinobject.org
Well, that's 5 lines, but it might actually work...
Note that here I've chosen to use the thinob tool to create the new object of the class. These are equivalent, except for error checking and such:
$ thinob foo.new MyClass
and
$ mkdir foo; ln -s ~/lib/thinob/MyClass foo/^
I'd also, confusingly perhaps, created the new foo object before defining the cpuinfo method -- maybe it would be better to finish the one before doing the other...
Except that with the class symlink in place, there's more direct (well, shorter) access to the class directory through the object, so:
$ mkdir ~/lib/thinob/MyClass;
$ mkdir foo; ln -s ~/lib/thinob/MyClass foo/^
$ echo cat /proc/cpuinfo > foo/^/cpuinfo
$ chmod +x foo/^/cpuinfo; thinob foo.cpuinfo
Well, that's now 4 lines, plus (at least) 2 others in the sig, so not quite there yet. But close enough for now.