I should mention that I know nothing about this problem domain other than what I just read in that wikipedia article...

I'd say the one issue you should consider is that someone might have a need for the exact functionality your module provides, only with a slightly different g-code output. Given that, you might consider structuring your code to allow for changing the output target. That way, if someone comes along and finds that your output doesn't work on his machine, he could just add a new output target. Of course, I don't have a clue about how difficult that would be given your current code. If you can do that, then a somewhat generic name like one of the ones that Corion suggested would make a lot of sense.

If you take another route, it might make sense to be more specific with your name. (I.e. call it GCode::Generator::Fanuc::Gears or something.) That would leave room for someone to come along later and write a generic GCode::Generator module that handles the output target and could use your module and other modules like Gcode::Generator::BCL::Gears when someone writes them.

-sauoq
"My two cents aren't worth a dime.";