Mirar @ Pike developers forum wrote:
I'm not sure how your module is intended to use, but if it'll be
linked into the module system under Sql.something, or never should be
called by the user, the _ is probably a good idea as an indicator for
that.
Ok, then I guessed correctly.
--
Sincerely,
Peter Bortas @ Pike developers forum wrote:
As long as you don't break compilation and doc generation and make the
appropriate CHANGES entries.
Quick question about naming the cmod. I currently ad-hoc named it PGsql.
Consequently I have a PGsql/PGsql.cmod etc.
Is there any point in naming it
