RE: Downside to namespacing
Mike wrote:
> My suggestion is to drop all exported variables and provide an interface
> of routines that allow multiple object functionality. Now, I have not
> seen the module to guage an idea of how complicated this might be but in
> the large programs I have (am) working on it hasn't taken that much
> extra effort.
The first thing I see wrong with this idea is the additional code and bugs
which will be introduced. The second thing is the added layer of indirection,
which may make a difference when loading a large list into a listview, for
instance.
A third problem is going to be more complex calls. And I see no way to avoid
exporting
at least one thing: the handle to the listview itself. That is necessary if
*anything* is going to be done to the list. In addition, since listviews use
the M/V/C scheme, I would have to create a lookup table to associate the various
list stores, iterators, etc with the correct listview. All in all, it's way
easier to just copy and rename the one, simpler file.
Irv
|
Not Categorized, Please Help
|
|
