Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address Validation moved to static method #2

Merged
merged 9 commits into from
Jun 21, 2011
Merged

Address Validation moved to static method #2

merged 9 commits into from
Jun 21, 2011

Conversation

ghost
Copy link

@ghost ghost commented Jun 18, 2011

Moved the validation of the ipv6 address in the construct to a public static method. This allows testing of an ipv6 address (to be valid or not) without throwing an exception.

… static function. This allows testing of an ipv6 address (to be valid or not) without throwing an exception.
Moved the validation of an IPv6 address from the constructor to the new public static method. This allows testing of an address to be valid or not without throwing an exception when creating an instance of the ipv6address object.
@ghost
Copy link
Author

ghost commented Jun 19, 2011

Modified the commit message. Hope it is ok now... (as me being a complete git newbie, used to subversion)

Corrected method documentation to properly define param and return value of the validation ipv6 method
Modified the validation in class methods to use the (new) public static validate method from the v6tools\IPv6Address class
Added 2 unittests for testing the public static method validate in IPv6Address vclass
Replaced logical and for or in checking validity of ipv6 prefix length
dsp added a commit that referenced this pull request Jun 21, 2011
Address Validation moved to static method
@dsp dsp merged commit d4780db into dsp:master Jun 21, 2011
@dsp
Copy link
Owner

dsp commented Jun 21, 2011

thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants