Hi Lars, Are you sure there is no way to achieve this by having some methods extending some interface? Your list classes just have to implement some common interface. You know like this:
Module ListInterface_Extensions MyCoolFunction extends LIF as ListInterface //dosomething here Am 05.06.2006 21:51 Uhr schrieb "[EMAIL PROTECTED]" unter <[EMAIL PROTECTED]>: > This seems like a specific instance of a more general problem. For > instance, I often find myself writing classes that are lists of > various things. With judicious naming, the only difference between the > various list classes is the type of thing being listed. I'd like to be > able to create a "template" class, method, or module that centralizes > all the repetitive logic, and just leaves the type unspecified. - Maximilian Tyrtania | [EMAIL PROTECTED] fischerAppelt Kommunikation GmbH Tucholskystr.18 | D-10117 Berlin | Germany Tel. ++49-30-726146-728 http://www.fischerappelt.de -- _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
