Re: Module submission ctflags

[Salvador Fandiņo]

Hi,

A . Bergman wrote:

    2) it's more a pragma than a normal module and pragmas usually have
    top level names

Does it change things compile time?

yes, everything in ctflags occurs at compile time... actually the "ct" in the name stands for compile time.

The purpose of ctflags is to define flags that could be used to conditional compile Perl code. i.e.:

MyApp.pm______________________________________

package MyApp;

use ctflags prefix=>'dbg_', 'myapp:debug:*'

sub bar {
$f=foo();

dbg_f and warn "foo return $f"; # [1]

print "bar!\n\n"
}

sub foo {
# ...
}

1;


sample.pl_____________________________________

use ctflags::parse ns=>'myapp:debug',
env=>'SAMPLEDEBUG'; # [2]

use MyApp;

MyApp::bar()


command_line__________________________________

$ SAMPLEDEBUG=f perl sample.pl
foo return whatever at MyApp line...
bar!

$ SAMPLEDEBUG='' perl sample.pl
bar!

______________________________________________

dbg_f [1] value is set from the env var 'SAMPLEDEBUG' in [2]. If its value is 0 perl will optimize out all the sentence.

The initial purpose of this module was to mimic the C preprocessor idiom to activate/deactivate debugging code in programs. i.e:

#ifdef DEBUG_SOCKET
/* C socket debugging code */
#endif

It also reassembles the usage of the perl -D switch to control perl debugging where you can use letters to select which subsystems to debug.


Bye,

- Salva