Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: Not too cool

by fgudin (Monk)
on Jun 17, 2016 at 07:28 UTC ( [id://1165951]=note: print w/replies, xml ) Need Help??


in reply to Not too cool

I don't think the length is at fault here. The Node Status says:

(…) Edit: code tags not paired. OPer /msgd.

Replies are listed 'Best First'.
Re^2: Not too cool
by marto (Cardinal) on Jun 17, 2016 at 07:35 UTC

    There is a limit on post size. Possibly the remainder of the code and the closoing tag was missing as consequence.

Re^2: Not too cool
by anita2R (Scribe) on Jun 17, 2016 at 11:24 UTC
    fgudin

    The tags were all matched, and the post appeared correct in preview, but as soon as it was 'created' it went haywire. I tried it three times!

    When I looked at the post which was said to have unmatched tags, I could see that part of the stuff I posted was missing, so it seems to be a length issue

      Hello anita2R,

      If you follow BrowserUk’s advice (as you should) then it may help you to know where your original post ended. Here’s my best reconstruction of the final subroutine:

      BTW, it’s no longer considered good practice to call a subroutine using an ampersand prefix, which has the effect of circumventing prototypes. Unless you have a good reason to do this (and you usually won’t), omit the prefix:

      $message = replaceCc( $message );

      From perlsub:

      A subroutine may be called using an explicit & prefix. The & is optional in modern Perl, as are parentheses if the subroutine has been predeclared. The & is not optional when just naming the subroutine, such as when it's used as an argument to defined() or undef(). Nor is it optional when you want to do an indirect subroutine call with a subroutine name or reference using the &$subref() or &{$subref}() constructs, although the $subref->() notation solves that problem.

      Hope that helps,

      Athanasius <°(((><contra mundum Iustus alius egestas vitae, eros Piratica,

        Athanasius

        Thanks. I have removed most of the POD documentation from within the code, leaving only brief help documentation.

        This brings the code down in size enough to post within the limit. I won't include the other files including the full POD help file unless someone asks for it.

        I will go back and change the subroutine calls, but it will take a while to test that all works well. I will repost in due course

      Perhaps there are one or more logical subdivisions of the code?

      If so, re-post the first chunk in the root node and add the rest as one or more posts subordinate to it.


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
      In the absence of evidence, opinion is indistinguishable from prejudice. Not understood.

        BrowserUk

        There are some logical sections, but I think I have reduced it sufficiently by removing POD documentation, to post it in one go.

        If it still doesn't work, I will take your advice and split the code at logical sections

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1165951]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having a coffee break in the Monastery: (5)
As of 2024-03-28 23:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found