Hello Anonymous,
Thank you for reviewing my code.
Well I am using (5.006) because in the source code of Time::HiRes, the author using this version. Since I am using the module I assumed I should not have higher version. The die syntax I picked it up from the Net::SNMP source code. I thought it is more tricky and nice to write it like this.
The only reason that I am using named subroutines, is to assist my self why I did something in future. I know that most of my functions only apply once in the code, but I assumed that this is the way to remember what I was trying to do in future.
Unused Variables such as @arraySendSntpPacket etc. could be inlined, but they help me to debug the code easier than defining all the variables one by one and printing them. Also for future when I will be updating the code it would make it easier to remember why e.g. a variable is 0 or 3 because it is li _vn_mode.
Yes I have prepared a few tests that cam to my mine with the basic version that I want to release. I am planning to release also a bit more complicated version updating the internal clock based on user preference. One step at a time.
In reply to Re^2: RFC: Net::SNTP::Server v1
by thanos1983
in thread RFC: Net::SNTP::Server v1
by thanos1983
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |