ποΈ Deprecate backward compatible parameters to new and starttls
#175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since 2007,
.newand#starttlshave taken an options hash (bad0027) and the original parameters have been undocumented (e631911). The originalusessl,certs, andverifyparameters will now print a deprecation warning whenever they are used. In a future release (no sooner than a year after 0.4.0 is released), they will be removed from both methods.The
optionshash has been converted to keyword parameters. An. sendingportas the second argument to#initializeis also obsolete. Neither of them will print a deprecation warning, but they will be marked as deprecated in a future release.To simplify the implementations of both
#initializeand#starttls, the backwards compatible parameters have all been extracted to aDeprecatedClientOptionsmodule, which is (currently) prepended toNet::IMAP.Note: #174 accidentally included rdoc references to
DeprecatedClientOptions, which is added by this PR.