From: Denis BEURIVE <lists@...>
Date: 2013-05-28T22:11:15+09:00
Subject: GEM and module? Could a GEM be a module?

Hello,

I have written a library that calculates dates based on CRON
specifications. I'd like to publish it as a GEM.

In order to avoid name collisions, I create a module ("Cron") that holds
all the classes that build the library. In fact the is two classes :

Cron::Calendar
Cron::NoNextExecution

In your code, you write : c = Cron::CronCalendar.new(...)

As you may wish, the second class represents an exception that is raised
if it is not possible to find the date of the next execution (this may
occur if the CRON specification defines a range for the year). I
included this class within a module because the name of the class may be
used in another context (that is, in another GEM). For example, you
write a workflow processor... You may want to define an exception
"NoNextExecution".

My question is :

Is it correct to say : "my GEM is a module" ?

Or should I "remove" the classes from the module ? (that is: no module
at all). But in this case, name collisions may occur.

Best regards,

Denis

-- 
Posted via http://www.ruby-forum.com/.