Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deconfuse language name and compiler in -v and -V #4647

Closed
p6rt opened this issue Oct 14, 2015 · 6 comments
Closed

deconfuse language name and compiler in -v and -V #4647

p6rt opened this issue Oct 14, 2015 · 6 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Oct 14, 2015

Migrated from rt.perl.org#126359 (status was 'resolved')

Searchable as RT126359$

@p6rt
Copy link
Author

p6rt commented Oct 14, 2015

From @TimToady

09​:39 < TimToady> HLL​::Compiler is very confused about what is the language
name/version vs compiler name/version, and this shows up in both -v and -V
09​:40 < TimToady> "This is perl6 version 2015.09-373-g254c1a8"
09​:42 < TimToady> should be more like "This is rakudo version
2015.09-373-g254c1a8 implementing Perl v6b" or so

(well, that, and it should still mention the backend version too)

@p6rt
Copy link
Author

p6rt commented Oct 14, 2015

From @TimToady

On Wed Oct 14 09​:46​:18 2015, larry wrote​:

09​:39 < TimToady> HLL​::Compiler is very confused about what is the language
name/version vs compiler name/version, and this shows up in both -v and -V
09​:40 < TimToady> "This is perl6 version 2015.09-373-g254c1a8"
09​:42 < TimToady> should be more like "This is rakudo version
2015.09-373-g254c1a8 implementing Perl v6b" or so

(well, that, and it should still mention the backend version too)

Also, make sure the Perl version is stored in only one place. In addition to the HLL​::Compiler spot, we currently have​:

./core/Perl.pm​: :$!version = Version.new("6b"),
./Perl6/Grammar.nqp​: my $vhave := $*W.find_symbol(['Version']).new('6.b'); # XXX need to use same source as Version.pm

1 similar comment
@p6rt
Copy link
Author

p6rt commented Oct 14, 2015

From @TimToady

On Wed Oct 14 09​:46​:18 2015, larry wrote​:

09​:39 < TimToady> HLL​::Compiler is very confused about what is the language
name/version vs compiler name/version, and this shows up in both -v and -V
09​:40 < TimToady> "This is perl6 version 2015.09-373-g254c1a8"
09​:42 < TimToady> should be more like "This is rakudo version
2015.09-373-g254c1a8 implementing Perl v6b" or so

(well, that, and it should still mention the backend version too)

Also, make sure the Perl version is stored in only one place. In addition to the HLL​::Compiler spot, we currently have​:

./core/Perl.pm​: :$!version = Version.new("6b"),
./Perl6/Grammar.nqp​: my $vhave := $*W.find_symbol(['Version']).new('6.b'); # XXX need to use same source as Version.pm

@p6rt
Copy link
Author

p6rt commented Dec 15, 2015

From @jnthn

On Wed Oct 14 10​:10​:14 2015, larry wrote​:

On Wed Oct 14 09​:46​:18 2015, larry wrote​:

09​:39 < TimToady> HLL​::Compiler is very confused about what is the
language
name/version vs compiler name/version, and this shows up in both -v
and -V
09​:40 < TimToady> "This is perl6 version 2015.09-373-g254c1a8"
09​:42 < TimToady> should be more like "This is rakudo version
2015.09-373-g254c1a8 implementing Perl v6b" or so

(well, that, and it should still mention the backend version too)

Also, make sure the Perl version is stored in only one place. In
addition to the HLL​::Compiler spot, we currently have​:

./core/Perl.pm​: :$!version = Version.new("6b"),
./Perl6/Grammar.nqp​: my $vhave :=
$*W.find_symbol(['Version']).new('6.b'); # XXX need to use same
source as Version.pm

Factored it out, both removing the special case in NQP and the duplication inside of Rakudo. Both -v and -V now carry the correct info.

@p6rt
Copy link
Author

p6rt commented Dec 15, 2015

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Dec 15, 2015

@jnthn - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Dec 15, 2015
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant