Re^4: Perl Modules

makes 100 % perfect sense. my code is not OO, though - except for when i use the core modules perl comes with (like CGI and others)...but, does your example work in my case? should i be making my modules generate objects, instead of how i have it setup (i posted code in another reply to my main post)? sounds like a major overhaul if so. this project needs completion. I'm a one man band, and it's been in dev. for 3yrs now (two drafts, and one "final" version)... clearly i'm new at this perlmonks.org site, so if i'm doing things that don't adhere to what you would rather see, allow me to apologize. i'll figure it out as i go. like i said, as a one man band, i feel like i'm the only employee for a large hotel - i gotta be everything. so many hats, it's been a very tough learning curve.

Comment on Re^4: Perl Modules

Replies are listed 'Best First'.
Re^5: Perl Modules by stevieb (Canon) on Jun 20, 2017 at 21:23 UTC
You do not need to change to OO. It was simply an example, which did include using a non-OO based module (`WiringPi::API`). My above example shows the same type of usage, but without any OO at all. Using OO is a personal preference, or when you need to keep the state of things.	[reply] [d/l]
Re^6: Perl Modules by jamroll (Beadle) on Jun 20, 2017 at 22:03 UTC
ah, alright. well, i'm not at all familiar with that Wiring module...i am reading everyone's posts though, and heeding all the advice very carefully. so many thanks. every tidbit of info i get will help. i had thought about converting to OO - at least for the user.pm module...but, i'm not saavy with OO in any language. it, too, is confusing.	[reply]