Re^4: $VERSION in module files

Not necessarily. If you maintain a version number for the dist which applies also to all the modules then you can pick one master module which all the others use and have them set their versions from that one. eg.

inheriting a version number is like inheriting your fathers age/birthdate

yeah my wife just gave birth to a beautiful baby, 9lbs, 32 years old

Comment on Re^4: $VERSION in module files Download Code

Replies are listed 'Best First'.
Re^5: $VERSION in module files by soonix (Canon) on Mar 27, 2020 at 04:23 UTC
Yes and no. It can also be like having different birthdays for your limbs. It might make sense for a peg leg, but mostly unnecessary. Depends on how interdependent the modules are.	[reply]
Re^6: $VERSION in module files by Anonymous Monk on Mar 27, 2020 at 07:52 UTC
Yes and no. It can also be like having different birthdays for your limbs. It might make sense for a peg leg, but mostly unnecessary. Depends on how interdependent the modules are. Hi, If its mostly unnecessary, what would be the point of inheriting a version number? Just ask the head	[reply]
Re^7: $VERSION in module files by soonix (Canon) on Mar 27, 2020 at 08:12 UTC
ITYM s/inheriting/carrying/ Yes, if modules are always being maintained together and not independently. However, there's always the possibility of people taking parts (e.g. modules) of one thing to use it elsewhere. Then it's easier if they all do carry their version info.	[reply]
Re^8: $VERSION in module files by bliako (Monsignor) on Mar 28, 2020 at 14:07 UTC


Pathologically Eclectic Rubbish Lister
	PerlMonks