Mark Engelberg wrote: > Here's the scenario I'm looking at: > A macro is used to convert a certain syntactic sugar into a function > call. I want to keep the function private, but provide the sugarized > macro version to other modules. > > Just 'provide the macro but not the function in you module should suffice this need. Chongkai