From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: zasprintf
Date: Sun, 17 Sep 2000 05:37:50 +0000 [thread overview]
Message-ID: <1000917053751.ZM18817@candle.brasslantern.com> (raw)
In-Reply-To: <20000917002552.A31354@dman.com>
On Sep 17, 12:25am, Clint Adams wrote:
} Subject: Re: PATCH: zasprintf
}
} > This seems to me to be the wrong way to approach this issue. If you
} > can't provide a non-broken implementation -- and I don't see how you
} > can, if you don't plan to implement a printf-format-string parser --
}
} I don't think it's impossible to provide a non-broken implementation;
I don't think it's impossible either, but the only way to "provide a
compatibility function for vsnprintf()" is to implement a parser for
printf format-strings. There simply is no way to fake it if you don't
have it. I don't believe there's any use zsh could make of asprintf()
that isn't better solved another way. In particular:
} > 3) Pasting a string obtained from readdir() onto a known path prefix.
} > In this case, it would be sufficient to use NAME_MAX + strlen()
} > (and use pathconf() to get NAME_MAX if necessary).
}
} I'm uncomfortable with this after the other pathconf episode, especially
} since pathconf() might return -1 for NAME_MAX, and then we've got
} to deal with that by either arbitrarily setting a value or by dynamically
} resizing, whereas I presume asprintf() would be cleaner and more
} efficient.
I don't have any such confidence that asprintf() would be cleaner or more
efficient than, say, a realloc'ing version of tricat() that takes a char**
to an allocated string as its first parameter.
As for pathconf() ... as far as I can tell NAME_MAX has none of the odd
problems associated with PATH_MAX. It doesn't, for example, potentially
vary from call to call within the same directory. The only tricky bit
is dealing with -1, which brings us back to the realloc'ing tricat().
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-09-17 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-16 18:53 Clint Adams
2000-09-17 0:47 ` Bart Schaefer
2000-09-17 1:10 ` PATH_MAX again Bart Schaefer
2000-09-17 4:25 ` PATCH: zasprintf Clint Adams
2000-09-17 5:37 ` Bart Schaefer [this message]
2000-09-17 15:04 ` Clint Adams
2000-09-17 16:13 ` Bart Schaefer
2000-09-17 16:43 ` Clint Adams
2000-09-17 12:21 ` Zefram
2000-09-18 13:28 ` Andrej Borsenkow
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=1000917053751.ZM18817@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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/zsh/
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).