News for hackers. Stuff that matters.
Re:The GNU extension language by jrockway on Saturday November 26, 2011 @04:35AM (#3279505)
The naming convention for macros is a little weird. My rule is: if the macro is user-visible (and not something to make your module easier to implement), it should start with define- or with-, and should include a uniquifier somewhere in the name. If you were writing an extension called foo, you might provide a macro called with-current-foo or define-foo-bar.

If someone already has a macro with this name, then don't call it that.

The reason for ignoring the normal package-function naming convention is that it's simply ugly to write code like:

   (eproject-with-current-project "foo" (whatever))
when you could write

   (with-current-project "foo" (whatever))
Re:The GNU extension language by gruseom on Saturday November 26, 2011 @12:42PM (#3280242)
I get (and practice) the part about user-visible macros. But what about macros that are just to make my module easier to implement? I often write those to concisify (well, you did say "uniquifier") my code. There's a tension here: encoding the package name in the macro name can easily make the name so long that the whole thing is why-bother, but using a short name runs the risk of a collision. For example, paredit.el defines XCOND. Although I don't have an XCOND, that's just the sort of macro name I might have chosen.