comment on

You said "...the instructions you will find would be specific to that module"

I don't think these are meant to be specific to a particular module. And I answered the question about how to learn C. It was Rhetorical. You learn it with instructions. My problem with instructions isn't that they don't apply to things they aren't meant to apply to, unless they mislead you into thinking they do.

I don't mind cross references, or "issues I need to note," but too often I don't even find that level of help from instructions.

If it's really that difficult to use modules requiring C, then there should be a warning about that. I shouldn't even have to "browse" the files to see that there are C files. "Compiling" sounds simple, as though you just point a compiler at the script. It seems like it should require the most basic instructions to allow me to do it for my OS (XP) and version/build of Perl.

In reply to Re^6: Keep "Free MSVC tools + Activestate to compile CPAN Modules" on front page! by Wassercrats
in thread Keep "Free MSVC tools + Activestate to compile CPAN Modules" on front page! by Wassercrats

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.


We don't bite newbies here... much
	PerlMonks