The script is a webserver that deals with the scheme of a directory service. At the starting of the program, the list is empty, and then with the first connection to the directory, the list is initialized according to the object classes and their settings (like attributes-names and their status (mandatory or optional), format, ...). The scheme of the directory changes sometimes, and the script will recognize these changements automatically and adapt the object interface methods to them.
The calls to these objects are generated by user input, so some objectclasses may not be used for a long time, while others are used very often.
And with autoload, I can get easy error messages if somehow an object interface method is called that is not allowed.
The problem with AUTOLOAD and inheritance is no problem in this case.
Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"
In reply to Re: Re: Re: is autoload bad style?
by strat
in thread is autoload bad style?
by racer_x
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |