mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: getopt_long permutation algorithm questions
Date: Wed, 03 Dec 2014 20:43:09 +0100	[thread overview]
Message-ID: <1417635789.4789.35.camel@eris.loria.fr> (raw)
In-Reply-To: <20141203192929.GA14223@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]

Am Mittwoch, den 03.12.2014, 14:29 -0500 schrieb Rich Felker:
> As part of resolving the rest of the dist-local changes Alpine is
> applying to musl, I'm trying to figure out how to add GNU-style
> argument permutation to getopt_long. The basic concept is simple: when
> a non-option argument is encountered, skip forward until the next
> option (argument beginning with '-') and move it (and possibly its
> argument) before the non-option arguments. However, there are some
> ugly corner cases like:
> 
> arg1 -ab foo arg2
> 
> where 'a' and 'b' are options, and 'b' takes an argument, foo. Here it
> seems like, in order to perform the correct permutation, lookahead is
> required to see that foo also needs to be moved. Is this correct?
> 
> For long options, it's immediately decidable from the option being
> processed whether it has no argument, or an argument that's part of
> the same argv[] string, or a separate option in the next argv[] slot.
> For short options, it seems necessary to scan each character of the
> argv[] string to be moved, looking for the first option that takes an
> argument. If none is found, or if such a character is found in a
> non-final position, only this string needs to be moved. If an option
> needing an argument is found in the final position, two argv[] strings
> need to be moved. Is this correct?

sounds all a bit complicated and fragile to me.  getopt should neither
be performance nor memory critical, so there is not much need for
optimization here, no?

Why don't you just keep track of the cases in an array on the stack,
and then do all the moves after the processing in a second scan? You
have argc, so you know the size of a VLA (`char[argc]` should suffice)
that you would have to define.

Jens
-- 
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-12-03 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 19:29 Rich Felker
2014-12-03 19:43 ` Jens Gustedt [this message]
2014-12-03 19:56   ` Rich Felker
2014-12-03 20:47     ` Jens Gustedt
2014-12-04  0:04       ` Rich Felker
2014-12-04  6:25         ` Timo Teras
2014-12-06 17:47           ` Rich Felker
2014-12-06 19:22             ` Rich Felker

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=1417635789.4789.35.camel@eris.loria.fr \
    --to=jens.gustedt@inria.fr \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).