Works for the small dataset, and I have moved to a live example, in which some of the methods already have headers and we want to leave them alone.

Input snippet:

/// <summary> /// Checks to see if the data on the clipboard supports /// the given data type. /// </summary> /// <param name="dataType">The data type to check for.</param> /// <returns><c>true</c> if the data type is present.</returns +> public bool ClipboardDataHasType(string dataType) { return dataType == m_dataType; } /// <summary> /// Gets the clipboard data. /// </summary> /// <param name="dataType">Type of the data.</param> /// <returns> /// The data on the clipboard matching the datatype /// </returns> public object GetClipboardData(string dataType)
gets turned into output snippet:
/// <summary> /// Checks to see if the data on the clipboard supports /// the given data type. /// </summary> /// <param name="dataType">The data type to check for.</param> /// <returns><c>true</c> if the data type is present.</returns +> /// <summary> /// public bool ClipboardDataHasType(string dataType) /// </summary> /// <param name="dataType">string</param> public bool ClipboardDataHasType(string dataType) { return dataType == m_dataType; } /// <summary> /// Gets the clipboard data. /// </summary> /// <param name="dataType">Type of the data.</param> /// <returns> /// The data on the clipboard matching the datatype /// </returns> /// <summary> /// public object GetClipboardData(string dataType) /// </summary> /// <param name="dataType">string</param> public object GetClipboardData(string dataType)
Basically, the if ($file =~ /$comment$method/) { line is never matching, where $method is the declaration line and $comment is:
\\s*///\\s*<summary>\\s*///.*\\n\\s*///\\s*</summary>\\n(\\s*///.*\\n) +*
This is the case whether I specify s, m, or both (in either sequence) for the matching.

In reply to Re^6: regex subst not DWIM by girarde
in thread regex subst not DWIM by girarde

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.