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

ops2c.pl seems to be obsolete #954

Closed
wants to merge 5 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 0 additions & 1 deletion MANIFEST
Expand Up @@ -2153,7 +2153,6 @@ tools/build/c2str.pl []
tools/build/fixup_gen_file.pl []
tools/build/gen_version.pl []
tools/build/h2inc.pl []
tools/build/ops2c.pl [devel]
tools/build/parrot_config_c.pl []
tools/build/pbcversion_h.pl []
tools/build/pmc2c.pl [devel]
Expand Down
2 changes: 0 additions & 2 deletions compilers/opsc/src/Ops/File.pm
Expand Up @@ -18,8 +18,6 @@ Ops::File - Ops To C Code Generation
C<Ops::File> takes one or more files of op functions and
creates real C code for them.

This class is used by F<tools/build/ops2c.pl>.

=head2 Op Functions

For ops that have trivial bodies (such as just a call to some other
Expand Down
7 changes: 0 additions & 7 deletions compilers/opsc/src/Ops/Op.pm
Expand Up @@ -24,11 +24,6 @@ Ops are either I<auto> or I<manual>. Manual ops are responsible for
having explicit next-op C<RETURN()> statements, while auto ops can count
on an automatically generated next-op to be appended to the op body.

Note that F<tools/build/ops2c.pl> supplies either 'inline' or 'function'
as the op's type, depending on whether the C<inline> keyword is present
in the op definition. This has the effect of causing all ops to be
considered manual.

=head2 Op Arguments

Note that argument 0 is considered to be the op itself, with arguments
Expand Down Expand Up @@ -687,8 +682,6 @@ our multi sub indent(%c) {

=item C<Ops::OpTrans>

=item F<tools/build/ops2c.pl>

=back

=head1 HISTORY
Expand Down
5 changes: 2 additions & 3 deletions config/init/defaults.pm
Expand Up @@ -251,9 +251,8 @@ sub runstep {
# Extra flags needed for libnci_test.so
ncilib_link_extra => '',

# Flag determines if pmc2c.pl and ops2c.pl also
# generate #line directives. These can confuse
# debugging internals.
# Flag determines if pmc2c.pl also generates #line directives.
# These can confuse debugging internals.
no_lines_flag => $conf->options->get('no-line-directives') ? '--no-lines' : '',

tempdir => File::Spec->tmpdir,
Expand Down
1 change: 0 additions & 1 deletion lib/Parrot/Manifest.pm
Expand Up @@ -246,7 +246,6 @@ sub _get_special {
languages/t/harness [test]
lib/File/Which.pm [devel]lib
src/vtable.tbl [devel]src
tools/build/ops2c.pl [devel]
tools/build/pmc2c.pl [devel]
tools/dev/create_language.pl [devel]
tools/dev/gen_makefile.pl [devel]
Expand Down
2 changes: 1 addition & 1 deletion t/perl/Parrot_Distribution.t
Expand Up @@ -68,7 +68,7 @@ for my $dir (@old_directory_list) {
my @perl_files = $d->get_perl_language_files();
ok( @perl_files, 'Got some perl files' );

ok( $d->perl_source_file_with_name('ops2c.pl'), 'Perl source file (.pl)' );
ok( $d->perl_source_file_with_name('pmc2c.pl'), 'Perl source file (.pl)' );
ok( $d->perl_source_file_with_name('Distribution.pm'), 'Perl source file (.pm)' );
ok( $d->perl_source_file_with_name('perlcritic.t'), 'Perl source file (.t)' );
ok( !$d->perl_source_file_with_name('p5rx.t'), 'Not a Perl source file (.t)' );
Expand Down
24 changes: 0 additions & 24 deletions tools/build/ops2c.pl

This file was deleted.