Skip to content

Conversation

kix
Copy link
Contributor

@kix kix commented Feb 24, 2015

I believe having a non-static method for class instantiation is not something the documentation should encourage. It's much better to use a named constructor here (also note that TestObject class code isn't supplied).

I believe having a non-static method for class instantiation is not something the documentation should encourage. It's much better to use a named constructor here (also note that `TestObject` class code isn't supplied).
@timglabisch
Copy link
Contributor

yes, you're totally right!

@xabbuh
Copy link
Member

xabbuh commented Mar 7, 2015

This looks reasonable to me. 👍

@weaverryan
Copy link
Member

Sounds good to me - thanks Stepan!

weaverryan added a commit that referenced this pull request Mar 14, 2015
… (kix)

This PR was submitted for the 2.6 branch but it was merged into the 2.3 branch instead (closes #5043).

Discussion
----------

Switched the first example to a static constructor method

I believe having a non-static method for class instantiation is not something the documentation should encourage. It's much better to use a named constructor here (also note that `TestObject` class code isn't supplied).

Commits
-------

118513b Switched the first example to a static constructor method
@weaverryan weaverryan closed this Mar 14, 2015
@kix kix deleted the patch-2 branch September 14, 2015 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants