y illegal at the moment :) but probably easy to catch in the
> internals and than we've got a new gate to a welth of internal info :)
Why not a simple(!) magic hash, or an entire namespace?
print $PROC{"memory used"};
print $PROC::memory_used;
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
o filter out "illegal" tags - tags they weren't
supposed to use - but wanted to get them some markup, I did reuse the
PODdish inside-out markups for bold, italic, and underlined, which allowed
me to filter *all* tags out prior to processing.
This isn't a suggestion by any means, just a "here's what I did for this
problem."
--
Bryan C. Warnock
[EMAIL PROTECTED]
te perlindex
See C in L, L, and L
See C in L, and L.
I could see how indexing would/could be useful.
--
Bryan C. Warnock
([EMAIL PROTECTED])
't know how
> that could be implemented.
>
Perhaps index via X<>?
=head1 SUMMARY
C implements a type of construct known as Xing.
Syntax could be similar to L<>, with allowing index on one word or
phrase, while printing another.
X, from above.
Much finer contr
omplaints are the inability to
properly screen input for valid or duplicate bugs, the lack of a
tie-in to a CM process, and the dearth of administrators to manage the
system.)
--
Bryan C. Warnock
([EMAIL PROTECTED])
g
Perhaps nesting is a tad confusing.
=begin example | testing
foo;
=end
=begin example
Stuff;
=end
Or am I missing the point?
--
Bryan C. Warnock
([EMAIL PROTECTED])
