# Re: Why Class decls and API docs don't Match **URL:** \ **Category:** Ruby\ **Created:** [October 19, 2006, 1:07am UTC](https://www.ruby-forum.com/t/re-why-class-decls-and-api-docs-dont-match/72800 "2006-10-19T01:07:50Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![phrogz](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/p/2acd7d/32.png) [@phrogz](https://www.ruby-forum.com/u/phrogz)\ **Post date:** [October 19, 2006, 1:07am UTC](https://www.ruby-forum.com/t/re-why-class-decls-and-api-docs-dont-match/72800/1 "2006-10-19T01:07:50Z")
From: Ken B. [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] > I nevertheless do not know what the rationale is for not bringing > along the class methods of a module along with the instance > methods when > the module is included in a class. Not being matz (or nobu or such), I can only guess myself. However, I prefer it this way, since it means that I can have a module with utility methods and not have those utility methods spammed into my class when I include it. What might be nice, however, would be an “include\_and\_extend” type class method that does what you describe, setting up two parallel inheritance paths for the class methods and instance methods to the module.