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.
I think that to avoid confusion any pubblic and documented library should use it's own tags. You never know the usage a programmer might do of your library. It lets you debug stuff easier, avoid strange bugs and extend a function is a simpler way. Just as a stupid example, consider the situation where you are in a foo(struct TagItem *attrs) where you accepts your own tags plus URL_Open() ones; you can pass the whole tags array ptr without filtering tags, after having parsed your own ones. Now extend the example, making foo() calling other tags list functions. Ciao. Alfonso. ------------------------ 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/
