I am not a cool kid.

My linux machine died and i never replaced it.
But I recently needed to do some perl coding,
So i googled perl download windows and
Ended up at a site with dwim and strawberry perl.

I think it was on perl.org


As for the error message, i spaced out all the

=header

=cut

Lines.  No change.

I commented out the guts of every subroutine, one by one.
No change.

I ended up creating a new file and copying code chunks piece by piece.
The new file never produced the error.

I have no idea what the problem was.
The old file was possessed, I suppose.

Greg




On Wed, June 28, 2017 12:10 pm, Bill Ricker wrote:
> On Wed, Jun 28, 2017 at 11:13 AM, Greg London <[email protected]>
> wrote:
>
>
>> dwim perl
>
>
> ​i thought the cool kids on Windows (if that isn't already a
> contradiction) were using Chocolatey Perl this year (Vanilla => Strawbery
> => Chocolatey,
> ok, it's a naming convention of sorts), but whichever.
>
> If your POD lacks blank lines around =commands as your example above
> lacks them, that will confuse some parsers.​ I don't know that this is
> your problem but maybe
>
>
>
> --
> Bill Ricker
> [email protected] https://www.linkedin.com/in/n1vux
>
>


-- 

_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm

Reply via email to