# General API design question: FooError vs Foo::Error

**URL:** <https://www.ruby-forum.com/t/general-api-design-question-fooerror-vs-foo-error/63758>\
**Category:** Ruby\
**Created:** [June 18, 2006, 9:45pm UTC](https://www.ruby-forum.com/t/general-api-design-question-fooerror-vs-foo-error/63758 "2006-06-18T21:45:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/c57346/32.png) [@danielb](https://www.ruby-forum.com/u/danielb)\
**Post date:** [June 18, 2006, 9:45pm UTC](https://www.ruby-forum.com/t/general-api-design-question-fooerror-vs-foo-error/63758/1 "2006-06-18T21:45:29Z")

</div>

Hi all,

I’ve noticed that some libs have changed from a class like FooError to  
Foo::Error. Take a look at TimeoutError vs Timeout::Error, for example.

Is there a reason the latter is preferred these days? Just curious.

Regards,

Dan
