Grokbase
x

document '#define PERL_CORE' ???

View TopicPrint | Flat  Thread  Threaded
1) Dave Mitchell We don't currently mention PERL_CORE in perlguts.pod. I'm wondering whether we should mention it,...
| +1 vote (Anchor)
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
We don't currently mention PERL_CORE in perlguts.pod.

I'm wondering whether we should mention it, purely in the negative context of
stopping people cargo-culting it: i.e. just because they copied some XS from
a module that used it, doesn't mean that they should use it too.

Something along the lines of:

"Don't use this. It exposes the perl innards, which change between
releases and thus your code will break with every new release"

Also it means that someone who complains that their XS has broken can be
pointed at the docs.

--
My get-up-and-go just got up and went.
2) Rafael Garcia-Suarez Good idea. "Here there be tygers":)
| +1 vote (Anchor)
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
On 7 February 2010 23:15, Dave Mitchell <davem@iabyn.com> wrote:
> We don't currently mention PERL_CORE in perlguts.pod.
>
> I'm wondering whether we should mention it, purely in the negative context of
> stopping people cargo-culting it: i.e. just because they copied some XS from
> a module that used it, doesn't mean that they should use it too.
>
> Something along the lines of:
>
> "Don't use this. It exposes the perl innards, which change between
> releases and thus your code will break with every new release"
>
> Also it means that someone who complains that their XS has broken can be
> pointed at the docs.

Good idea. "Here there be tygers":)
3) Dave Mitchell Now done with 0972ecdf6decc0f53d00772c18026d31b7aaf416
| +1 vote (Anchor)
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
On Mon, Feb 08, 2010 at 09:54:18AM +0100, Rafael Garcia-Suarez wrote:
> On 7 February 2010 23:15, Dave Mitchell <davem@iabyn.com> wrote:
> > We don't currently mention PERL_CORE in perlguts.pod.
> >
> > I'm wondering whether we should mention it, purely in the negative context of
> > stopping people cargo-culting it: i.e. just because they copied some XS from
> > a module that used it, doesn't mean that they should use it too.
> >
> > Something along the lines of:
> >
> > "Don't use this. It exposes the perl innards, which change between
> > releases and thus your code will break with every new release"
> >
> > Also it means that someone who complains that their XS has broken can be
> > pointed at the docs.
>
> Good idea. "Here there be tygers":)

Now done with 0972ecdf6decc0f53d00772c18026d31b7aaf416

--
It's not that I'm afraid to die, I just don't want to be there when it
happens.
-- Woody Allen
spacer
View TopicPrint | Flat  Thread  Threaded
Home > Groups > Perl 5 Porters > document '#define PERL_CORE' ??? (3 posts)