I tried using source filters (Filter::Simple), but couldn't make it work, either. I usually don't use these, so i might have done it wrong.
Frankly, i would consider the use of a constant function (or other type of constant) for a port number a major bug in AnyEvent::DNS. There are very few use cases that make sense to declare a number a constant in programming code. Pi might qualify, but in my opinion even physics constants shouldn't (because, hey, i might want to run a simulation to see what would happen if i change the planck constant.
As for port numbers, if you want to run a network service as non-root (which is highly recommended, and pretty much a must while debugging software), the easiest way would be to change the port and set a fowarding rule on local the firewall. This is pretty much the default answer on most Linux forums. So coding a port number as constant in a library is a big no-no. Especially if it's a reserved port (lower than 1024).
I haven't reported this as a bug to the AnyEvent maintainers, since i don't use AnyEvent. This should be done by sectokia, since they can provide more information to the maintainers.
In reply to Re^2: How to redefine a modules private function?
by cavac
in thread How to redefine a modules private function?
by sectokia
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |