Function returning 2 arrays - which way to do so?

[jodleren]

Hi!

I have a function, a part of my code which I can use as a function. It
will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

1) setting the arrays as globals
2) returnin an array of arrays
3) returning a large array with a known marker to indicate when the
2nd part starts.

Any other ideas?
As of now, it will only be used in one place... but that might change.

WBR
Sonnich

[Erwin Moller]

jodleren wrote:

Hi!

I have a function, a part of my code which I can use as a function.

I have no clue what that sentence means. :P

It

will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

1) setting the arrays as globals
2) returnin an array of arrays
3) returning a large array with a known marker to indicate when the
2nd part starts.

Any other ideas?
As of now, it will only be used in one place... but that might change.

WBR
Sonnich

I would go with something like 2, because it is the most structured
approach in my opinion.

Something like this:

function gimme2(){
$arr1 = array("hi","bla ");
$arr2 = array("more","o f","this");
$returnThis = array();
$returnThis["arr1"] = $arr1;
$returnThis["arr2"] = $arr2;
return $returnThis;
}

// from code:
$result = gimme2();
// $result["arr1"] now contains first array, $result["arr2"] the second

Of course you can put the resulting arrays into a new var if that is
convenient, eg:
$result1 = $result["arr1"];
$result2 = $result["arr2"];

// unset $result maybe if not needed anymore
unset($result);

I prefer returning complex datastructures as hashed arrays, because I
can be more descriptive (like what holds what), but that is a matter of
taste.

Regards,
Erwin Moller

[Michael Fesser]

..oO(jodleren)

>I have a function, a part of my code which I can use as a function. It
will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

1) setting the arrays as globals

No.

>2) returnin an array of arrays

Possible.

>3) returning a large array with a known marker to indicate when the
2nd part starts.

No.

>Any other ideas?

4) Arguments passed by reference:

function foo(&$arg1, &$arg2) {
$arg1 = array(1, 2, 3);
$arg2 = array(4, 5, 6);
}

Micha

[jodleren]

On Jan 7, 11:15*am, Erwin Moller
<Since_humans_r ead_this_I_am_s pammed_too_m... @spamyourself.c omwrote:

jodleren wrote:

Hi!

It

will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

1) setting the arrays as globals
2) returnin an array of arrays
3) returning a large array with a known marker to indicate when the
2nd part starts.

Any other ideas?
As of now, it will only be used in one place... but that might change.

WBR
Sonnich

I would go with something like 2, because it is the most structured
approach in my opinion.

[snip]

>
I prefer returning complex datastructures as hashed arrays, because I
can be more descriptive (like what holds what), but that is a matter of
taste.

I tend to agree.

[=?ISO-8859-1?Q?thib=B4?=]

jodleren wrote:

Hi!

I have a function, a part of my code which I can use as a function. It
will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

1) setting the arrays as globals
2) returnin an array of arrays
3) returning a large array with a known marker to indicate when the
2nd part starts.

Any other ideas?
As of now, it will only be used in one place... but that might change.

WBR
Sonnich

Serialized in separated string.
Hmm ^^'

-thib´

[C. (http://symcbean.blogspot.com/)]

On 7 Jan, 09:15, Erwin Moller
<Since_humans_r ead_this_I_am_s pammed_too_m... @spamyourself.c omwrote:

jodleren wrote:

Hi!

I have a function, a part of my code which I can use as a function.

I have no clue what that sentence means. :P

It

will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

<snip>

I would go with something like 2, because it is the most structured
approach in my opinion.

Something like this:

function gimme2(){
$arr1 = array("hi","bla ");
$arr2 = array("more","o f","this");
$returnThis = array();
$returnThis["arr1"] = $arr1;
$returnThis["arr2"] = $arr2;
return $returnThis;

}

// from code:
$result = gimme2();
// $result["arr1"] now contains first array, $result["arr2"] the second

<snip>

>
I prefer returning complex datastructures as hashed arrays, because I
can be more descriptive (like what holds what), but that is a matter of
taste.

/me prefers not to explicitly create data structures which are only
used once:

function gimme2(){
$arr1 = array("hi","bla ");
$arr2 = array("more","o f","this");
return array($arr1, $arr2);
}

list($first, $second)=gime2( );

C.

[Logos]

On Jan 7, 2:34 am, Michael Fesser <[e-mail] wrote:

.oO(jodleren)

I have a function, a part of my code which I can use as a function. It
will return 2 arrays, and I am wondering what way to do so. Both
arrays hold strings, there are no special keys.

1) setting the arrays as globals

No.

2) returnin an array of arrays

Possible.

3) returning a large array with a known marker to indicate when the
2nd part starts.

No.

Any other ideas?

4) Arguments passed by reference:

function foo(&$arg1, &$arg2) {
$arg1 = array(1, 2, 3);
$arg2 = array(4, 5, 6);

}

Micha

I'll second this one. Passing in both arrays by reference is clean &
tidy, and a commonly accepted way for a function to 'return' more than
one value.

[Tim Roberts]

Logos <ty*********@gm ail.comwrote:

>
I'll second this one. Passing in both arrays by reference is clean &
tidy, and a commonly accepted way for a function to 'return' more than
one value.

That's true in C and C++, but only because there's no way to return several
things at once.

There are two issues with the reference solution. First, it requires the
caller to allocate arrays first, and then pass those arrays to the
function. In many cases, that's not natural. Second, it creates a high
degree of linkage between the callee and caller, which again may not be
natural.

Now, these are both highly philosophical issues, but there is good sense in
adapting a policy that things to be returned should always be "returned",
rather than by modifying in/out parameters.
--
Tim Roberts, ti**@probo.com
Providenza & Boekelheide, Inc.

[Logos]

On Jan 7, 11:23 pm, Tim Roberts <[e-mail] wrote:

Logos <tyler.st...@gm ail.comwrote:

I'll second this one. Passing in both arrays by reference is clean &
tidy, and a commonly accepted way for a function to 'return' more than
one value.

That's true in C and C++, but only because there's no way to return several
things at once.

There are two issues with the reference solution. First, it requires the
caller to allocate arrays first, and then pass those arrays to the
function. In many cases, that's not natural. Second, it creates a high
degree of linkage between the callee and caller, which again may not be
natural.

Now, these are both highly philosophical issues, but there is good sense in
adapting a policy that things to be returned should always be "returned",
rather than by modifying in/out parameters.
--
Tim Roberts, [e-mail]
Providenza & Boekelheide, Inc.

Well, I'll admit to a C background.

However, if you're going to offer a critique I think it's only fair to
report which solution you think best & why, no? We have several
options for things being returned :)

IMHO, I think this is one of those stylistic things that really
doesn't have a best answer. It doesn't really impact performance in
any way - all that it impacts is *how the coder* interacts with the
code.