
perlbug-followup at perl
Aug 10, 2013, 9:16 PM
Post #8 of 9
(13 views)
Permalink
|
|
[perl #119213] [PATCH] e915662 s/ajust/adjust/g
[In reply to]
|
|
On Sat Aug 10 18:00:56 2013, public [at] khwilliamson wrote: > On 08/10/2013 05:41 PM, James E Keenan via RT wrote: > > On Sat Aug 10 15:50:37 2013, mauke- wrote: > >> On Sat Aug 10 14:15:06 2013, jkeenan wrote: > >>> > >>> Would it be possible to submit a patch for that? > >>> > >> > >> Patch attachment attached. Is this what you meant? > > > > Yes. This passes all tests for me on Dromedary (linux/x86_64) with a > > plain configuration. But perhaps those with more C-fu than I should > > stare at it a bit. > > > > Thank you very much. > > Jim Keenan > > > > --- > > via perlbug: queue: perl5 status: open > > https://rt.perl.org:443/rt3/Ticket/Display.html?id=119213 > > > > It looks fine to me, though I don't think I would have bothered to move > the initialization of nbytes until after the ASSERT. > > I presume that the reason he did this was to take advantage of the > machine-generated ASSERT which asserts that nbytes_p is not NULL. Thus > if it is NULL, it will fail that assertion, rather than get a segfault > at the initialization of nbytes. I don't see much gain in in clarity > here, and, supposedly, declarations that also initialize are generally > faster than this way. > > But, one could argue either way, and the patch looks perfectly valid to > me, so I think you should apply it. > Thanks for the review. I have applied the patch in commit bbb3b2d37817afff967fe98df398ed218dde5410 . Since we have more than addressed the original subject of this RT, I am marking it resolved. Please open a new RT for any new problems. Thank you very much. Jim Keenan --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=119213
|