Re: SimpleXML's atXPath method

Hey all, Is there a major issue with simply adding a $limit parameter to the existing xpath() method instead, and stopping searching after that many elements are found? Cheers Stephen Sent from my iPhone > On 8 Jan 2017, at 06:19, Joe Watkins <pthreads@pthreads.org> wrote: > > Evening Rowan, > > Thank you. > > Now we can get to the really hard problem ... naming things :D > > I'm afraid I have no good suggestions. I can find API's that use the > suggested name, but they vary in functionality (some overlap). > > There's also XmlNode.SelectSingleNode from C#, but sounds pretty horrible > to me, variations on it might be: > > selectPath > singlePath > singleNode > > None of them really sound right to me, but may provoke someone else to do > better. > > Over to you, someone else ... > > Cheers > Joe > > On Sat, Jan 7, 2017 at 11:02 PM, Rowan Collins <rowan.collins@gmail.com> > wrote: > >>> On 07/01/2017 19:29, Joe Watkins wrote: >>> >>> Evening Roawn, >>> >>> There is no competition to see which single problem we are going to >>> solve, we can fix more than one thing, obviously :) >>> >>> What we are discussing here is the value of this particular feature, not >>> the value of things that nobody has taken the time to propose, implement, >>> or fix. >>> >>> This contributor has waited a year for this conversation to start, it >>> would be nice if we could stay focused. >> Indeed, I didn't mean to imply otherwise, and sorry if I gave that >> impression. There is a small cost to adding new methods like this, in >> future maintenance, and the future consistency of the extension, but you're >> right that it's not a big deal, and other than finding the right name, I've >> no real reason to object to this method. >> >> >> Regards, >> >> -- >> Rowan Collins >> [IMSoP] >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >>