Hello Henning, #?, On 28.11.05, Henning Thielemann wrote:
> For ordinary library functions TAG_USER should be ok as tag base. Only for > MUI tags more differentiated tag bases are necessary because functions > like SetAttrs and GetAttrs have to process tags of many custom classes and > thus of many different developers. These tags must not collide. I don't > see this problem for functions where no external extension is possible. changing a public API which is used in a lot programs is for sure the right opposite of smart. To limit the amount of damage done already it's prolly the best to bring back old tag values and use them parallel to the new ones and add some detailed info about this to documentation, so that developers who want to use the library know exactly that when they want to use the 'new' tags they also must open the library with a certain version. A cleaning up task for the new developers who jump in with the openurl sf.net project ;) -- .tokai - christian rosentreter @ http://www.christianrosentreter.com you notice things if you pay attention ------------------------ Yahoo! Groups Sponsor --------------------~--> Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/16uqlB/TM --------------------------------------------------------------------~-> Visit http://www.amiga.dk/tumult for MUI-related information, especially about MUI custom classes. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/MUI/ <*> 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/
