Sounds like fun!:
# IHeartFortran.pm
package IHeartFortran;
use strict; use warnings;
require Exporter;
our @ISA = qw( Exporter );
our @EXPORT = qw/ EQV NEQV /;
use overload '.' => \&_do_op;
sub _do_op {
my ($self, $y, $reverse) = @_;
$$self{ $reverse ? 'left' : 'right' } = $y;
if (exists($$self{left}) and exists($$self{right})) {
return $$self{op}->(@$self{qw/ left right /});
}
return $self;
}
sub new {
my ($class, $op) = @_;
bless { op => $op }, $class;
}
sub EQV() { __PACKAGE__->new( sub { $_[0] == $_[1] ? 1 : 0 } ) }
sub NEQV() { __PACKAGE__->new( sub { $_[0] != $_[1] ? 1 : 0 } ) }
Then to use it:
#!/usr/bin/perl
use strict; use warnings; use 5.010;
use IHeartFortran;
say 1 .EQV. 1;
say 1 .EQV. 2;
say 1 .NEQV. 1;
say 1 .NEQV. 2;
This doesn't exactly create a .EQV. operator (for instance, spaces would be allowed: 1 . EQV . 2), but it looks good enough.
update: Actually, I think FORTRAN's whitespace rules would allow extra spaces anyway, so perhaps this is a somewhat faithful recreation anyway. Case flexibility on the other hand...
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|