Namespace conflicts


#1

Good morning, everyone.

I’m curious as to how I can resolve some namespace conflicts. I’m
writing a
Rails app (although this problem should be agnostic), and wrote a
Payment
model (which is a class for those that don’t use Rails) for my app.

I also have need to use the Payment gem from ruby forge, which uses
‘Payment’ as the name for the module.

I obviously have a conflict here, but I’m wondering if anyone has any
interesting ideas as to how I can solve it.

As far as I see it, I’ll need to rename one of the two objects.

Thanks to everyone,

Michael


#2

Whoah. Thanks for that.


#3

On May 14, 2006, at 9:12 AM, Michael G. wrote:

I obviously have a conflict here, but I’m wondering if anyone has any
interesting ideas as to how I can solve it.

As far as I see it, I’ll need to rename one of the two objects.

Thanks to everyone,

Michael

Nest your app in it’s own namespace?

module Gorsuch
class Payment < ActiveRecord::Base

end
end

Gorsuch::Payment.new #etc.