I originally starting writing this as a bit of a joke, then I thought
perhaps I should submit it as a serious suggestion. Anyone violently
against or in favour? Is this even an issue that should go in a PDD?
Does anyone care? Should I return to my box now?
Dave M.
Not a joke, I find this to be a very valuable rule. No comments,
no check-ins.
I would define a relatively strict and standard way to do this so that
the documentation can be extracted out.
References: see perlapi and perlintern in the current development releases.
A related matter is that
On Mon, Feb 19, 2001 at 02:27:06PM +, Simon Cozens wrote:
On Mon, Feb 19, 2001 at 08:17:17AM -0600, Jarkko Hietaniemi wrote:
I would define a relatively strict and standard way to do this so that
the documentation can be extracted out.
I'd like to see Perl 6 written as a literate
On Mon, Feb 19, 2001 at 08:37:48AM -0600, Jarkko Hietaniemi wrote:
Hey, let's extend pod! Hey, let's use XML! Hey, let's use SGML! Hey,
let's use XHTML! Hey, let's use lout! Hey, ...
Can we take this to perl6-trivial-flamewars-markup-language, please? :)
--
"He was a modest,
On Mon, Feb 19, 2001 at 03:13:02PM +, Simon Cozens wrote:
On Mon, Feb 19, 2001 at 08:37:48AM -0600, Jarkko Hietaniemi wrote:
Hey, let's extend pod! Hey, let's use XML! Hey, let's use SGML! Hey,
let's use XHTML! Hey, let's use lout! Hey, ...
Can we take this to
Jarkko Hietaniemi wrote:
Some sort of simple markup embedded within the C comments. Hey, let's
extend pod! Hey, let's use XML! Hey, let's use SGML! Hey, let's use
XHTML! Hey, let's use lout! Hey, ...
Either run pod through a pod puller before the C preprocessor gets to
the code, or
I think "defined" should be altered so that it only looks like a function,
but in effect alters the tests being made by the thing that is looking at it.
if (defined $x){ # slower than if ($x){ # or if($x or defined($x))
could be made faster by propagating the "defined" question up