New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sv_vcatpvfn_flags and format string friends crash on numbered args #13085
Comments
From @bulk88Created by @bulk88Per Line 10452 in 6de85bb
perl's internal printf supports numbered index format string args. When I try to use them, for example
I *guess* (correct me if I am wrong) numbered args are only implemented I would like the numbered args to work for C stack varargs too, so my I'm not sure if this is a bug report, feature request, doc request, or Perl Info
|
From @hvdsbulk88 (via RT) <perlbug-followup@perl.org> wrote: [...] :I *guess* (correct me if I am wrong) numbered args are only implemented I think it's a feature request (though the docs may also be lacking). As I understand it, the way varargs are accessed you cannot find the n'th I think it would require a rather more complex process than the existing It would be worth looking at other implementations of this; here's an The C99 standard does not include the style using '$', .. which sounds like it's implementing something similar to what I describe There's a risk that introducing a bunch of extra complexity to this code So I'd be tempted to go for the fallback position first - make it recognise Hugo [1] Somehow, not sure how you do it with varargs; I suspect also that |
The RT System itself - Status changed from 'new' to 'open' |
From @hvdsOn Sat, 06 Jul 2013 01:46:07 -0700, hv wrote:
We don't have this. I think we're unlikely to get it.
We do have this, since 46e58bd: Document and ensure that sv_catpvf() does no argument ordering I'm not sure whether to leave this ticket as is, or mark it as one of stalled or rejected. I will mark it as wishlist though. Hugo |
Migrated from rt.perl.org#118775 (status was 'open')
Searchable as RT118775$
The text was updated successfully, but these errors were encountered: