On 05/01/02 23:33 -0800, Jeffrey Friedl wrote:
>
> I don't know how I never looked at Inline before today, but today I did,
> and I've got to say it's the most freaking cool thing I've seen since I
> first saw a CGI in action in 1994. All I can say is "wow".
I *will* quote you on that.
Hey, did Nat put you up to this? ;)
>
> I'm pleased to be able to help in even the most miniscule say, and it's
> with a doc bug report. The main 'perldoc Inline' docs say:
>
> |> If a particular config option has value options of 1 and
> |> 0, you can use the ENABLE and DISABLE modifiers. In other
> |> words, this:
> |>
> |> use Inline Config =>
> |> FORCE_BUILD => 1,
> |> CLEAN_AFTER_BUILD => 0;
> |>
> |> could be reworded as
> |>
> |> use Inline Config =>
> |> ENABLE => FORCE_BUILD,
> |> DISABLE => CLEAN_AFTER_BUILD;
>
> The right side of the => need to be quoted:
>
> ENABLE => 'FORCE_BUILD',
> DISABLE => 'CLEAN_AFTER_BUILD';
>
>
> Everyone uses 'strict', right? :-)
Actually, I'm guilty of not using strict in my Inline examples, just to make
them a teensy bit cleaner. You'll notice that I say the following just about
everywhere:
use Inline C;
In fact, it's even on the back of the Inline T-shirt. "strict" is for
wussies. ;)
Even though I'm a fan of keeping simple things *really* simple, I'll probably
apply your patch.
Thanks again for the accolades. And welcome to the club! :)
Cheers, Brian
