Hi guys,
I'm looking at writing a new version of ARB. It will no longer require a
'refresh' when aliases are added or removed, and depending on the
results of the new poll there will be dramatic changes to how aliases
are actually stored and referenced.
All of the proposed methods that the poll suggests have their advantages
and disadvantages. Here are a few:
* Keeping the alias definitions within the main ARB script means that
there is only one file to ever worry about. Unfortunately this
makes upgrading ARB slightly more difficult.
* Storing ARB aliases as scripts instead of labels eliminates the
need for an alias cache and the inherent rebuilding thereof. It
also allows labels to be used within them. (ARB would not treat
these labels in any special way.)
* Storing ARB aliases as scripts with a prefixed name makes calling
these aliases from outside ARB very easy.
I would greatly appreciate input from everyone using ARB regarding this
matter, and if anyone has any other ARB-related feedback then there's no
better time to share it!
--
Regards,
Alex Peters
Attention: PowerPro's Web site has moved: http://www.ppro.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/power-pro/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
