[RESOLVED] limit number of values added to implode()?

Joseph_Sliker

Hi;

Say I have a process that generates an array with a variable number of values, but that I really only want to return no more than the first 5 into an implode() 'ed string.

ie.

$picnames=array("pic1.jpg","pic2.jpg","pic3.jpg","pic4.jpg","pic5.jpg","pic6.jpg","pic7.jpg");

and I want to $allpics=implode("|",$picnames); (but limited to just the first five) and end up with a string like this:

$topfive="pic1.jpg|pic2.jpg|pic3.jpg|pic4.jpg|pic5.jpg";

Is there some substring function that will chop $allpics just before the fifth "|" appears, or something like that?

Thanks.

laserlight

[man]array_slice[/man] could come in handy, e.g.,

$picnames = array("pic1.jpg", "pic2.jpg", "pic3.jpg", "pic4.jpg", "pic5.jpg", "pic6.jpg", "pic7.jpg");
$allpics = implode("|", array_slice($picnames, 0, 5));

Note that instead of array() you could write:

$picnames = ["pic1.jpg", "pic2.jpg", "pic3.jpg", "pic4.jpg", "pic5.jpg", "pic6.jpg", "pic7.jpg"];

but maybe that's the Pythonista in me showing :p

Bonesnap

laserlight;11043117 wrote:
but maybe that's the Pythonista in me showing :p

I think of JavaScript when I see that!

Joseph_Sliker

laserlight!

$allpics = implode("|", array_slice($picnames, 0, 5));

Perfect! It works great. Thanks so much!

Derokorian

laserlight;11043117 wrote:
Note that instead of array() you could write:
$picnames = ["pic1.jpg", "pic2.jpg", "pic3.jpg", "pic4.jpg", "pic5.jpg", "pic6.jpg", "pic7.jpg"];
but maybe that's the Pythonista in me showing :p

Only if you're on 5.4+ 🙂

laserlight

Derokorian wrote:
Only if you're on 5.4+

5.3.x reached end of life more than a month ago. Time to upgrade 😉

dalecosp

laserlight;11043163 wrote:
5.3.x reached end of life more than a month ago. Time to upgrade 😉

AS IF the hosting companies are gonna do THAT anytime soon.

Oh, well, my personal VM on the East Coast and my development VM on the desktop are 5.5 and 5.4, respectively... perhaps I should find a new job. 😉

Derokorian

laserlight;11043163 wrote:
5.3.x reached end of life more than a month ago. Time to upgrade 😉

Unfortunately, when you're a small team serving 1.5Billion + requests a day - you tend to focus on the features people want, instead of removing the 7yr old code that's incompatible with 5.4+. We're close, we'll be able to get on 5.5 by the end of the year for sure.

Weedpacket

Derokorian wrote:
We're close, we'll be able to get on 5.5 by the end of the year for sure.

By which time you'll be able to look at upgrading to 5.6 🙂