# Re: toplevel namespace justification

**URL:** <https://www.ruby-forum.com/t/re-toplevel-namespace-justification/48008>\
**Category:** Ruby\
**Created:** [November 15, 2005, 10:23pm UTC](https://www.ruby-forum.com/t/re-toplevel-namespace-justification/48008 "2005-11-15T22:23:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel.Berger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ac8455/32.png) [@Daniel.Berger](https://www.ruby-forum.com/u/Daniel.Berger)\
**Post date:** [November 15, 2005, 10:23pm UTC](https://www.ruby-forum.com/t/re-toplevel-namespace-justification/48008/1 "2005-11-15T22:23:08Z")

</div>

> -----Original Message-----  
> From: Trans [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)]  
> Sent: Tuesday, November 15, 2005 1:07 PM  
> To: ruby-talk ML  
> Subject: toplevel namespace justification
> 
> When is using the toplevel constant namespace justified?

Whenever you’re not redefining methods for one of the core classes.

Otherwise, always use a namespace for your classes.

Regards,

Dan

---

<div class="post-metadata">

**Author:** ![Daniel.Berger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ac8455/32.png) [@Daniel.Berger](https://www.ruby-forum.com/u/Daniel.Berger)\
**Post date:** [November 15, 2005, 10:35pm UTC](https://www.ruby-forum.com/t/re-toplevel-namespace-justification/48008/2 "2005-11-15T22:35:14Z")

</div>

On Wed, 16 Nov 2005, Berger, Daniel wrote:

> Otherwise, always use a namespace for your classes.

indeed.

i also do

module M  
class C  
end  
end

module N  
C = M::C  
end

when required.

-a