>>>>> "BR" == Bill Ricker <[EMAIL PROTECTED]> writes:
>> return undef is a legit thing to return
>> and very different than return ;. plain return means don't change
>> anything but return undef means replace the data with undef.
BR> But plain return; returns undef in scalar context -- are you claiming
BR> this is always called in a list context so you can tell (undef) from
BR> () ?
yep. all filters are called with an assignment to an array. this is the
only way to detect return undef ; from return ;. so plain return will
not modify the data being filtered but return undef will replace it with
undef.
>> i made the dispatch table so you can easily add more markups to that
>> same syntax.
BR> Yup. Just having s{}{}ge call through a dispatch table was
BR> interesting. The Power of Perl.
one of the more fun things perl can do. :)
>> warnings? we don't need no steenking warnings!
BR> Just thinking of the business users you expect to update these pages
BR> in the future. The Pythonesque indented Pascalish BEGIN END macro
BR> language of the content pages doesn't seem very BU user friendly _for
BR> creation of new pages_; I'll believe business users could tweak
BR> content but not create it afresh.
i will claim work in progress again! the indenting is not manditory and
i use it for a visual aid. given what i have seen of simple markups
(wiki and others) and the need for tree structured data, this is the
compromise syntax i created. one important point is that this format is
not manditory at all. the format is controlled by the content file
suffix (another dispatch table! :) and it also suppports csv (used to
load the list of retail stores). so it would be easy to create and use
different content formats. i like this one so far even if i am the only
one so far to use it. it is as minimal as i can make it and also have
the tree stuff it needs. i spent many hours wrangling over this before i
went this way. all the other ideas were broken or too complex. there is
no BU easy way to do tree structures in plain text AFAICT. they can
cut/paste this easily (which i what i do most of the time). what is nice
is that you can have scalars on one or more than one line. and no array
markup is needed, just have multiple entries of the same name and it
does the right thing. the only part you have to really think about is
structures and nesting.
>> at least someone dared to read that mess. :)
BR> I still haven't found where Template::Simple gets invoked ...
in the render_page method. the Template::Simple is created only once and
used for all the pages to be rendered. should be easy to search for.
uri
--
Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
_______________________________________________
Boston-pm mailing list
Boston-pm@mail.pm.org
http://mail.pm.org/mailman/listinfo/boston-pm
