{"push_id":678984739,"size":191,"distinct_size":178,"ref":"refs/heads/merge-upstream","head":"bde2ac8925cb0cf64047cab920e8bf4e134264be","before":"74e857bde4e6fcd6ed3a8ca6157c8cae2be63e47","commits":[{"sha":"b7c1f088bbb124804cdec44fb11a94109473efed","author":{"email":"dc30e19244b61a39e80a3d0fa61957c198cbcee2@cpan.org","name":"Ricardo Signes"},"message":"CoreList: eliminate trailing spaces from some versions\n\nreported by perlancar, [perl #124364]","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/b7c1f088bbb124804cdec44fb11a94109473efed"},{"sha":"a31f9aef2d49956a5310036eb86435caf0e2dfb6","author":{"email":"b58d09249b3e367ae8383be7fc79efabb7794458@cpan.org","name":"Karl Williamson"},"message":"Regen podcheck db\n\nRecent commits have caused it to fail under -i-pedantic","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/a31f9aef2d49956a5310036eb86435caf0e2dfb6"},{"sha":"8560fbdd574815f9b1e6690cbac213446515ff2e","author":{"email":"b58d09249b3e367ae8383be7fc79efabb7794458@cpan.org","name":"Karl Williamson"},"message":"perlapi: Wrap long verbatim lines to 79 columns","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/8560fbdd574815f9b1e6690cbac213446515ff2e"},{"sha":"be59b6aaf8e201fef17a0706e99f6a47556ed1ac","author":{"email":"70be7c2737d249dddaefc49c432d14fdb71fe1bf@gmx.de","name":"Aristotle Pagaltzis"},"message":"correct the deprecation data in Module::CoreList","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/be59b6aaf8e201fef17a0706e99f6a47556ed1ac"},{"sha":"310a0d0a370ea21c004bfea4bbdd2cf15da94547","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@iabyn.com","name":"David Mitchell"},"message":"[perl #123737] Fix assertion failure with 0$#{\n\nThis is a follow-up to FC's 488bc579589, which stopped assertion\nfailures on parsing 0${. A similar code path still failed with\n0$#{.\n\nThe fix is similar to the previous fix, although I suspect a more general\nfix is needed - perhaps moving the fixes into S_no_op() - but not this\nclose to the 5.22 release.","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/310a0d0a370ea21c004bfea4bbdd2cf15da94547"},{"sha":"c22aa07d4f20e1eb10134bbc6f87b22c36b55512","author":{"email":"b58d09249b3e367ae8383be7fc79efabb7794458@cpan.org","name":"Karl Williamson"},"message":"perlhacktips: Nit, clarification","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/c22aa07d4f20e1eb10134bbc6f87b22c36b55512"},{"sha":"257844b92d3c10f7e307f63208d703bf01f713fb","author":{"email":"b58d09249b3e367ae8383be7fc79efabb7794458@cpan.org","name":"Karl Williamson"},"message":"perlhacktips: Add character set portability tip","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/257844b92d3c10f7e307f63208d703bf01f713fb"},{"sha":"05039abd64c611f39e792c9c6546c4795fb96ada","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@iabyn.com","name":"David Mitchell"},"message":"op_sibling_splice(): handle custom ops\n\nop_sibling_splice() decides whether a parent op has an op_last field\nthat needs updating based on the op's class. However, it it didn't\nhandle OP_CUSTOM ops.\n\nSpotted by Zefram.","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/05039abd64c611f39e792c9c6546c4795fb96ada"},{"sha":"4ad0ecd4c5a81ed8f71804b908656dca23f4867e","author":{"email":"008d58476d874a2ebeb53355997f9d338b6dab17@cpan.org","name":"Karen Etheridge"},"message":"move the documentation for $] out of the deprecated section","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/4ad0ecd4c5a81ed8f71804b908656dca23f4867e"},{"sha":"d2578154934acc58c35260d46623962e12848748","author":{"email":"008d58476d874a2ebeb53355997f9d338b6dab17@cpan.org","name":"Karen Etheridge"},"message":"add back documentation that $OLD_PERL_VERSION is an alias for $]","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/d2578154934acc58c35260d46623962e12848748"},{"sha":"b77ebf74c6d61f12ef717fd4bd6f765479481ca1","author":{"email":"70be7c2737d249dddaefc49c432d14fdb71fe1bf@gmx.de","name":"Aristotle Pagaltzis"},"message":"Also restore the index entry for $OLD_PERL_VERSION\n\nThis was missed in d2578154934acc58c35260d46623962e12848748.","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/b77ebf74c6d61f12ef717fd4bd6f765479481ca1"},{"sha":"122af3100408d1e1ee6b6583ec1d84a85f0a0f3a","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@iabyn.com","name":"David Mitchell"},"message":"avoid uninit read in re_op_compile()\n\nSome code in this function examines the first two nodes in the regex to\nset suitable flags etc. Part of the code accesses the second node\nby using regnext(first), other parts by NEXTOPER(first). The second method\nonly works when the node is the same size as a basic node. I *think*\nthat the code only makes use of this second value in situations where\nthe node *is* basic, but nevertheless, it makes valgrind unhappy when\nthe first node is an EXACT node, and reading the second node's\nsupposed type field is actually reading the padding bytes at the end of\nthe EXACT string, which are uninitialised.\n\nSo just use regnext() only.\n\nSomething as simple as /x/ on non-debugging builds was enough to make\nvalgrind complain. (On debugging builds, the program buffer is initially\nzero-filled.)","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/122af3100408d1e1ee6b6583ec1d84a85f0a0f3a"},{"sha":"996de84d864e2452987ceb29dbf56f1ce92846b8","author":{"email":"b58d09249b3e367ae8383be7fc79efabb7794458@cpan.org","name":"Karl Williamson"},"message":"PATCH: [perl #124348] re/pat_advanced solaris failure\n\nTony Cook traced this down to a compiler bug.  But it's easy to change\nthe code to avoid the problem.  The expression evaluates to 0; and was\nonly in the form that caused the failure to document what was going on.\nNow, instead the failed form is shown in comments, and 0 is used\ndirectly.","distinct":false,"url":"https://api.github.com/repos/rurban/perl/commits/996de84d864e2452987ceb29dbf56f1ce92846b8"},{"sha":"86c35584cf8f9ac2d46d63defc137216cd8e6df9","author":{"email":"70be7c2737d249dddaefc49c432d14fdb71fe1bf@gmx.de","name":"Aristotle Pagaltzis"},"message":"POSIX: Regeneralize export.t to non-ASCII platforms\n\nThis reverts commit 2da5b9bef2ef557a6978ec45042e29fa38e9bade and solves\nthe problem by sorting the expectation data instead, to make sure it is\nconsistent with the sort order of the comparison data. This removes the\nneed to depend on another file.","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/86c35584cf8f9ac2d46d63defc137216cd8e6df9"},{"sha":"57e88091a0a502716610aeeade5461e8e8a2192a","author":{"email":"b58d09249b3e367ae8383be7fc79efabb7794458@cpan.org","name":"Karl Williamson"},"message":"perlunicode: Update nonchars discussion for Unicode 7.0\n\nUnicode 7.0 changed the prohibition of noncharacters to merely \"not\nrecommend\" their use.  Perl continues to forbid them in strict input\nchecking (otherwise security issues could arise), but the discussion\nabout them needs to be updated to correspond with their new status.\n\nThe message raised when they are used probaby should change\ncorrespondingly, but it is too late for 5.22 for that.\n\nThis commit deletes some text elsewhere about the noncharacter code\npoints.  This text really wasn't germane to a discussion about UTF-8\n(wherein it appeared), as the encoding is irrelevant to these code\npoints.  They're not recommended in any UTF format.\n\nUnicode spells the term \"noncharacter\" without a hyphen.  This pod\nchanges to follow that spelling.","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/57e88091a0a502716610aeeade5461e8e8a2192a"},{"sha":"b12396ac84cef7e23e1aac516fa676165ddfc790","author":{"email":"1001e8702733cced254345e193c88aaa47a4f5de@develop-help.com","name":"Tony Cook"},"message":"[perl #124187] don't call pad_findlex() on a NULL CV","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/b12396ac84cef7e23e1aac516fa676165ddfc790"},{"sha":"de0885da327045eed274d7f8913a58e6de0e0f30","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@iabyn.com","name":"David Mitchell"},"message":"null ptr deref in Perl_cv_forget_slab\n\nRT #124385\n\nParsing following a syntax error could result in a null ptr dereference.\n\nThis commit contains a band-aid that returns from Perl_cv_forget_slab() if\nthe cv arg is null; but the real issue is much deeper and needs a more\ngeneral fix at some point.\n\nBasically, both the lexer and the parser use the save stack, and after an\nerror, they can get out of sync.\n\nIn particular:\n\n1) when handling a double-quoted string, the lexer does an ENTER, saves\nmost of its current state on the save stack, then uses the literal string\nas the toke source. When it reaches the end of the string, it LEAVEs,\nrestores the lexer state and continues with the main source.\n\n2) Whenever the parser starts a new block or sub scope, it remembers the\ncurrent save stack position, and at end of scope, pops the save stack back\nto that position.\n\nIn something like\n\n    \"@{ sub {]}}  }}}\"\n\nthe lexer sees a double-quoted string, and saves the current lex state.\nThe parser sees the start of a sub, and saves PL_compcv etc. Then a parse\nerror occurs. The parser goes into error recovery, discarding tokens until\nit can return to a sane state. The lexer runs out of tokens when toking\nthe string, does a LEAVE, and switches back to toking the main source.\nThis LEAVE restores both the lexer's and the parser's state; in particular\nthe parser gets its old PL_compcv restored, even though the parser hasn't\nfinished compiling the current sub. Later, series of '}' tokens coming\nthrough allows the parser to finish the sub. Since PL_error_count > 0, it\ndiscards the just-compiled sub and sets PL_compcv to null. Normally the\nLEAVE_SCOPE done just after this would restore PL_compcv to its old value\n(e.g. PL_main_cv) but the stack has already been popped, so PL_compcv gets\nleft null, and SEGVs occur.\n\nThe two main ways I can think of fixing this in the long term are\n1) avoid the lexer using the save stack for long-term state storage;\nin particular, make S_sublex_push() malloc a new parser object rather\nthan saving the current lexer state on the save stack.\n2) At the end of a sublex, if PL_error_count > 0, don't try to restore\nstate and continue, instead just croak.\n\nN.B. the test that this commit adds to lex.t doesn't actually trigger the\nSEGV, since the bad code is wrapped in an eval which (for reasons I\nhaven't researched) avoids the SEGV.","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/de0885da327045eed274d7f8913a58e6de0e0f30"},{"sha":"775e571870df24da0c43e0c911ccb42ddec687a0","author":{"email":"fe08d3c717adf2ae63592e4c9aec6e3e404d8e3e@iabyn.com","name":"David Mitchell"},"message":"fix weird comment in cop.h blurb\n\nThe original blurb which I added to the top of cop.h had an ambiguous\nstatement in it that sometime later got \"corrected\" into the wrong\nmeaning.","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/775e571870df24da0c43e0c911ccb42ddec687a0"},{"sha":"778a883eed767a9726757209f122f06909f86bdf","author":{"email":"dc30e19244b61a39e80a3d0fa61957c198cbcee2@cpan.org","name":"Ricardo Signes"},"message":"perldelta: import changes from perl5211delta.pod\n\nWhat about perl5210delta, you ask?  It had no changes of note beyond\nmodule changes.","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/778a883eed767a9726757209f122f06909f86bdf"},{"sha":"2f8e054cd01f977fda546d7761a76c2d8e37b19a","author":{"email":"dc30e19244b61a39e80a3d0fa61957c198cbcee2@cpan.org","name":"Ricardo Signes"},"message":"perldelta: import changes from perl5212delta.pod","distinct":true,"url":"https://api.github.com/repos/rurban/perl/commits/2f8e054cd01f977fda546d7761a76c2d8e37b19a"}]}