<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Calling functions with named arguments</title>
	<link>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/</link>
	<description>Mr Quinn, one word for your fans? "Ehm, astronaut."</description>
	<pubDate>Fri, 21 Nov 2008 04:18:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Life according to Gordon &#187; Blog Archive &#187; No, PHP does not suck; YOU suck</title>
		<link>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/#comment-426</link>
		<dc:creator>Life according to Gordon &#187; Blog Archive &#187; No, PHP does not suck; YOU suck</dc:creator>
		<pubDate>Thu, 05 Jun 2008 05:25:41 +0000</pubDate>
		<guid>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/#comment-426</guid>
		<description>[...] makes a difference (first parameter, second parameter, etc.). A little while back I saw a really neat implementation of calling functions with named arguments, that I've actually extended a bit on my own using [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] makes a difference (first parameter, second parameter, etc.). A little while back I saw a really neat implementation of calling functions with named arguments, that I&#8217;ve actually extended a bit on my own using [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Holmström</title>
		<link>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/#comment-7</link>
		<dc:creator>Fredrik Holmström</dc:creator>
		<pubDate>Tue, 25 Mar 2008 18:18:10 +0000</pubDate>
		<guid>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/#comment-7</guid>
		<description>Well the first argument that I can come up with is that it the function signature looks a lot cleaner, and the default values are easier to spot then with a $func_args = array_merge($default, $func_args)-call.

The array_key_exists (or well, personally I would use isset()) approach isn't viable unless you have complete control over the source of the functions, plus it pollutes the function code with things it shouldn't have to care about.</description>
		<content:encoded><![CDATA[<p>Well the first argument that I can come up with is that it the function signature looks a lot cleaner, and the default values are easier to spot then with a $func_args = array_merge($default, $func_args)-call.</p>
<p>The array_key_exists (or well, personally I would use isset()) approach isn&#8217;t viable unless you have complete control over the source of the functions, plus it pollutes the function code with things it shouldn&#8217;t have to care about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bucky</title>
		<link>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/#comment-6</link>
		<dc:creator>bucky</dc:creator>
		<pubDate>Tue, 25 Mar 2008 17:47:10 +0000</pubDate>
		<guid>http://loveandtheft.org/2008/03/23/reflection-calling-methodsfunctions-with-named-arguments/#comment-6</guid>
		<description>hmm, how about you just pass an array to begin with, and check inside of your func for array_key_exists. work with the language instead of against it lol!</description>
		<content:encoded><![CDATA[<p>hmm, how about you just pass an array to begin with, and check inside of your func for array_key_exists. work with the language instead of against it lol!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
