There are two features which I think would be good to have in
EmbperlObject. I would like to know what you think:
1. The ability for Execute() to look up the directory tree if it can't find
the named file, in the same way that the EMBPERL_OBJECT_BASE is searched
for. This would enable more true object-orientation than at present, where
a file that tries [- Execute ('../file.html') -] will fail if the parent
directory has no file.html. However file.html may exist further up the
hierarchy, in which case that one should be found. This is more object
oriented. A workaround is to place an almost-empty proxy file.html at every
level of the directory hierarchy, each one calling its parent, but this
seems clumsy and unnecessarily clutters up the directories, making it
difficult to tell at a glance which files have really been overridden in
any particular directory.
2. The ability for Execute() to recognise multiple instances of the same
filename. Why? Because if the filename is something like '../file.html',
then you may want to have this a few times in Execute() statements as they
work up the directory hierarchy, calling parents which have the same
filename. But Embperl fails because they all look like the same filename.
Again, a workaround exists - you can create a uniquely named symbolic link
in every subdirectory, which points to the parent directory (..). But this
also seems clumsy and unintuitive, and requires extra setup for any new
subdirectory.
These two features would make EmbperlObject even more useful and also make
it easier to construct ambitious websites which use extensive inheritance.
I hope this is the right place to bring these issues up...
What do you think? If any of this is unclear then let me know and I will
supply a more concrete example.
Thanks for your time!
-Neil Gunton
NilSpace Inc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
