Announce: Macro.pm - macro pre-processor with embedded perl capability
sum...@chest.ac.uk
This bundle consists of a module which may be used in your scripts and a
tiny program which uses the module. The module provides a small macro
language which includes the following commands:
%DEFINE
%DEFINE_SCRIPT
%UNDEFINE
%LOAD
%INCLUDE
%CASE
Wherever macro/script names are found in the source they (and their
optional parameters) are replaced with the body of the macro definition
(or the result of the execution of the script in the case of script
definitions).
If an embedded perl approach is preferred this can be achieved by using
the supplied 'macro' program which will only perform replacements within
the specified delimiters.
See
http://www.cpan.org/modules/by-authors/id/S/SU/SUMMER/
__________________________________________
sum...@chest.ac.uk http://www.chest.ac.uk
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
John Porter
>Macro.pm - macro pre-processor with embedded perl capability
Apparently you found it necessary to ignore the instructions in
04pause.html:
talk to mod...@perl.org before you decide upon the namespace
as well as section 2.5 of 00modlist.long.html:
use a nested module name to informally group or categorise a
module, e.g., placing a sorting module into a Sort:: category.
choose an already-existing category when possible.
Send mail to mod...@perl.org before you upload, so we can
help you select a name.
You never brought up the issue of naming this module
on mod...@perl.org or any of the perl newsgroups. But it's not
too late to fix it. You can rename the module and upload it again,
with a note in the README that it supercedes the earlier upload.
But before you do that, I highly recommend studying 04pause.html, and
at least section 2 of 00modlist.long.html.
Thanks, and have a nice day,
John Porter
Randal L. Schwartz
John> Apparently you found it necessary to ignore the instructions in
John> 04pause.html:
John> talk to mod...@perl.org before you decide upon the namespace
John> as well as section 2.5 of 00modlist.long.html:
John> use a nested module name to informally group or categorise a
John> module, e.g., placing a sorting module into a Sort:: category.
John> choose an already-existing category when possible.
John> Send mail to mod...@perl.org before you upload, so we can
John> help you select a name.
Not to mention that there are already 35 ways of doing this. I wonder
what a 36th way would add. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<mer...@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
John Porter
>
>Not to mention that there are already 35 ways of doing this. I wonder
>what a 36th way would add. :)
Actually, that would be a good reason to leave the name as it is --
so it stays "private". Maybe there should be a "Dustbin" category.
Or "Oubliette". (jk :-)
--
John Porter
sum...@chest.ac.uk
1. There may be 35 ways of doing this (although they aren't listed), but
I always thought that there was more than one way of doing things and
that different ways suited different people/contexts. There are many
modules for processing command line options for example.
2. I did fail to ask mod...@perl.org for advice on naming. I did read
the PAUSE information - but some time ago, and had forgotten this. I
will rectify that mistake.
3. I am mystified as to why the final comment was made. If the module is
faulty then say what's wrong with it, but what contribution does being
rude make, other than to say "I'm a real perl hacker you're just an
amateur, so don't bother".
Regards.