From: Fiona Ebner <f.ebner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH storage] style: remove goto statements
Date: Thu, 27 Jun 2024 15:28:20 +0200 [thread overview]
Message-ID: <0f408152-898c-4bd7-97fe-91bb727f6a02@proxmox.com> (raw)
In-Reply-To: <20240626085617.3343314-1-f.gruenbichler@proxmox.com>
Am 26.06.24 um 10:56 schrieb Fabian Grünbichler:
> these can just as well be `die` statements right there, there is no complicated
> cleanup that would warrant a goto statement..
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
but with some suggestions:
> ---
> src/PVE/Storage/Plugin.pm | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/src/PVE/Storage/Plugin.pm b/src/PVE/Storage/Plugin.pm
> index b5a54c1..f8dc9a2 100644
> --- a/src/PVE/Storage/Plugin.pm
> +++ b/src/PVE/Storage/Plugin.pm
> @@ -1586,13 +1586,14 @@ sub read_common_header($) {
> # Export a volume into a file handle as a stream of desired format.
> sub volume_export {
> my ($class, $scfg, $storeid, $fh, $volname, $format, $snapshot, $base_snapshot, $with_snapshots) = @_;
While at it, we could add a blank line here ;)
> + my $unsupported = "volume export format $format not available for $class\n";
Maybe add _msg or _error or similar to improve the variable name?
> if ($scfg->{path} && !defined($snapshot) && !defined($base_snapshot)) {
> my $file = $class->path($scfg, $volname, $storeid)
> - or goto unsupported;
> + or die $unsupported;
Could be moved to the previous line.
> my ($size, $file_format) = file_size_info($file);
>
> if ($format eq 'raw+size') {
> - goto unsupported if $with_snapshots || $file_format eq 'subvol';
> + die $unsupported if $with_snapshots || $file_format eq 'subvol';
> write_common_header($fh, $size);
> if ($file_format eq 'raw') {
> run_command(['dd', "if=$file", "bs=4k", "status=progress"], output => '>&'.fileno($fh));
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-06-27 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 8:56 Fabian Grünbichler
2024-06-27 13:28 ` Fiona Ebner [this message]
2024-07-01 8:50 ` [pve-devel] applied: " Fabian Grünbichler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f408152-898c-4bd7-97fe-91bb727f6a02@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox