> On 28 Jun 2017, at 14:01, Martin Barth wrote:
> but your approach means you have to state the version in the META6.json AND
> in the Module.pm6 file again. This would be the similar to having $VERSION in
> perl5. Shouldnt there be a simpler way?
Isn’t that info available
See I'm using mi6 to generate my META6.json file from the report and it
picks the version up from the module file. Other options like that seem
sensible to me.
Simon
On Wed, 28 Jun 2017, 13:01 Martin Barth, wrote:
> Hello,
>
> but your approach means you have to state the
Hello,
but your approach means you have to state the version in the META6.json
AND in the Module.pm6 file again. This would be the similar to having
$VERSION in perl5. Shouldnt there be a simpler way?
Am 28.06.2017 um 08:45 schrieb Fernando Santagata:
Hi Martin,
This works for me:
File
Hi Martin,
This works for me:
File mytest.pm6
use v6;
unit module mytest:ver<0.0.1>;
sub myver is export
{
mytest.^ver;
}
File mytest.p6
#!/usr/bin/env perl6
use lib '.';
use mytest;
say myver;
Console output:
$./mytest.p6
v0.0.1
I this what you meant?
On Tue, Jun 27, 2017 at 10:37