Re^2: Module Architecture

This is most helpful indeed, I have recreated my module again and again before managing to create a plan that could be easily expanded on.

About the top level namespace I thought about using something along the lines of Linux::Net, since security is only used for some offense tools and network for old MSN management code I'm not sure it would be a good idea to use either of those...

Comment on Re^2: Module Architecture

Replies are listed 'Best First'.
Re^3: Module Architecture by VinsWorldcom (Prior) on Aug 24, 2015 at 18:16 UTC
I use Perl almost exclusively on Windows, but the code I write can be used cross-platform - as is the intention for most Perl code. Is your module(s) truly only for Linux? Otherwise, I certainly would not include 'linux' in the distribution name.	[reply]
Re^4: Module Architecture by QuillMeantTen (Friar) on Aug 24, 2015 at 18:40 UTC
Thing is it will very probably be, depending on the way I implement IPC... Have a look at my dilemna Since I dont think an implementation usint unix sockets would be crossplatforms I might be left with named pipes for everything on one host and inet sockets for everything else :( Anyway my project is a long way from being done, I have a lot of modules to write to even get the skeleton done so I guess I'll have time to think about it. Still, why would it be such a bad idea to start a top level name?	[reply]
Re^5: Module Architecture by VinsWorldcom (Prior) on Aug 24, 2015 at 18:48 UTC
More information here http://pause.perl.org/pause/query?ACTION=pause_namingmodules. ---------- NAMES TO AVOID ... Top-level namespaces In general, top level namespaces are bad, ...	[reply]
Re^6: Module Architecture by QuillMeantTen (Friar) on Aug 24, 2015 at 18:51 UTC

NAMES TO AVOID

Top-level namespaces