Your assert function won't be able to see lexical variables.

my $x = 42; assert '$x > 40'; # assertion fails, # because eval can't see $x

Better is to write assert so that it takes a code ref...

sub assert (&) { require Carp; (shift)->() ? 1 : Carp::croak('Assertion failed') } my $x = 42; assert { $x > 40 }; # assertion ok

Also, I'd recommend giving your pseudo-constants TRUE, FALSE and EXIT_SUCCESS an empty prototype - i.e. () - and not using the return keyword in them. This allows the Perl compiler to treat them as real constants - inlining them into code that calls them. And if will solve your problems that lead them to occasionally needing to be called with a leading &.

sub TRUE () { 1 } sub FALSE () { 0 } sub EXIT_SUCCESS () { TRUE }
use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

In reply to Re: C and other stuff by tobyink
in thread C and other stuff by perlaintdead

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.