<div dir="ltr">+1<br><br><div class="gmail_quote">On Mon, Sep 29, 2008 at 10:22 PM, David Chelimsky <span dir="ltr">&lt;<a href="mailto:dchelimsky@gmail.com">dchelimsky@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The convention for gems is that the top level module shares a name<br>
with the gem, but rspec uses &#39;spec&#39; instead, resulting in things like<br>
this:<br>
<br>
require &#39;rubygems&#39;<br>
gem &#39;rspec&#39;<br>
require &#39;spec&#39;<br>
<br>
I&#39;d like to propose that we change the &#39;spec&#39; namespace to &#39;rspec&#39;.<br>
We&#39;d have to continue to support &#39;spec&#39; for backwards compatibility<br>
for a long time, but we can do that with a few extra files that just<br>
require other files.<br>
<br>
Thoughts?<br>
_______________________________________________<br>
rspec-devel mailing list<br>
<a href="mailto:rspec-devel@rubyforge.org">rspec-devel@rubyforge.org</a><br>
<a href="http://rubyforge.org/mailman/listinfo/rspec-devel" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dean Wampler<br><a href="http://www.objectmentor.com">http://www.objectmentor.com</a><br><a href="http://www.polyglotprogramming.com">http://www.polyglotprogramming.com</a><br>
<a href="http://www.aspectprogramming.com">http://www.aspectprogramming.com</a><br><a href="http://aquarium.rubyforge.org">http://aquarium.rubyforge.org</a><br><a href="http://www.contract4j.org">http://www.contract4j.org</a><br>

</div>