Because of the way I learned Perl, I usually edit in my favorite text editor (vim in linux, Notepad++ in windows) and run in the command line, and debug using copious print statements. :-).
But for Windows development, I have followed the advice of Notepad++ Integrated Perl Debugging and occasionally use Notepad++ as a front-end for interactive debug when my print-ing isn't sufficient. There are 32bit and 64bit versions of Notepad++, but the DBGP plugin is only available for the 32bit version. However, I successfully use the 32bit Notepad++ on 64bit Windows on a daily basis, and haven't found any problems. And that setup can call either my 32bit or my 64bit Strawberry Perl, whichever I point it to, so the bitness of the editor doesn't influence the choice in the bitness of the interpreter. But it's a quirky setup, so I wouldn't go so far as to "recommend" it -- I use it, but not always, so it's probably best to just list it as a potential, not the "best" or "recommended".
-
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.
|