Let's suppose you have an abstract class, say, RestApiRequest. Your class' user should interit it (let's name it MyRestApiRequest) and implement some methods (for example "response_callback" for handle response), and also define some parameters to tune class behaviour - in our example it will be "timeout" for http request.
This timeout is not per-object, but global for all objects of user's class (same timeout for all API requests for this API vendor). In this case good solution is not to pass timeout to constructor and not to set timeout as object field in constructor, but to define MyRestApiRequest::timeout which will return timeout (a scalar), usually it will be a constant:
package MyRestApiRequest; use parent RestApiRequest; sub response_callback { # some code } sub timeout { 42 } 1;
Question is:
What about:
package MyRestApiRequest; use parent RestApiRequest; use constant timeout => 42; sub response_callback { # some code } 1;
i.e. we have constant here, instead of method. techncally it's same. Is this acceptable? Good style or not? Any drawbacks? Have you seen this before?
In reply to Using constants as methods by vsespb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |