mirror of
https://github.com/openssl/openssl.git
synced 2024-12-21 06:09:35 +08:00
1aa89a7a3a
They now generally conform to the following argument sequence:
script.pl "$(PERLASM_SCHEME)" [ C preprocessor arguments ... ] \
$(PROCESSOR) <output file>
However, in the spirit of being able to use these scripts manually,
they also allow for no argument, or for only the flavour, or for only
the output file. This is done by only using the last argument as
output file if it's a file (it has an extension), and only using the
first argument as flavour if it isn't a file (it doesn't have an
extension).
While we're at it, we make all $xlate calls the same, i.e. the $output
argument is always quoted, and we always die on error when trying to
start $xlate.
There's a perl lesson in this, regarding operator priority...
This will always succeed, even when it fails:
open FOO, "something" || die "ERR: $!";
The reason is that '||' has higher priority than list operators (a
function is essentially a list operator and gobbles up everything
following it that isn't lower priority), and since a non-empty string
is always true, so that ends up being exactly the same as:
open FOO, "something";
This, however, will fail if "something" can't be opened:
open FOO, "something" or die "ERR: $!";
The reason is that 'or' has lower priority that list operators,
i.e. it's performed after the 'open' call.
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/9884)
|
||
|---|---|---|
| .. | ||
| poly1305-armv4.pl | ||
| poly1305-armv8.pl | ||
| poly1305-c64xplus.pl | ||
| poly1305-ia64.S | ||
| poly1305-mips.pl | ||
| poly1305-ppc.pl | ||
| poly1305-ppcfp.pl | ||
| poly1305-s390x.pl | ||
| poly1305-sparcv9.pl | ||
| poly1305-x86_64.pl | ||
| poly1305-x86.pl | ||