Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

You have my sympathy for your bad feelings, but maybe all is not lost. I learned Perl before I learned C# and .Net, and maybe right now it is hard to believe but C# can be almost as much fun as Perl.

I recommend that you explore the Regex support in .Net (System.Text.RegularExpressions). You should know that it is a publicly stated goal for the .Net framework to be compatible with Perl 5 - and on top of that it adds features like named captures.

One of the things I miss most about Perl is the one-liners, but then I think I can leave this as idiomatic of Perl and be content.

I don't think your Perls of wisdom will be devoured, remind yourself that you will always know that there's another way to do things, and whenever you want you can

perl -e "while(<>){s/abc/def/ig; print}"

...while all those around you are doing

using System; using System.IO; using System.Text.RegularExpressions; namespace YourCompanyName { class myClass { public static void Main() { StreamReader sr = new StreamReader(); ...and on and on and on... } } }

 


In reply to Re: Murder of a Perl coder (announced) by EdwardG
in thread Murder of a Perl coder (announced) by Discipulus

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.