comment on

That's awesome!

I ordered a couple of them for myself. One to play with, the other I'm going to write some tests for after connecting it to my test platform.

After going through the code, your module uses WiringPi::API, but your cpanfile lists RPi::WiringPi. The latter requires the former, and since I don't see any usage of RPi::WiringPi anywhere in the code, might I recommend that you change your prereq to WiringPi::API instead? The installation of your distribution will go *much* faster if you do this.

RPi::WiringPi installs a whole slew of sensor, ICs and other peripheral distributions (Perl and XS) that takes quite some time. If you're not using any of the functionality of this encompassing distribution, it's best if you don't require it.

In reply to Re^2: Is Perl on the Raspberry Pi worth it? by stevieb
in thread Is Perl on the Raspberry Pi worth it? by stevieb

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.


Don't ask to ask, just ask
	PerlMonks