[kdewebdev-site] Local test bench and defined variables

Eric Laffoon eric at kdewebdev.org
Tue Mar 8 14:55:05 EST 2005


On Tuesday 08 March 2005 12:59 pm, Andras Mantia wrote:
> On Tuesday 08 March 2005 22:48, Andras Mantia wrote:
> > I cannot believe this does not work in PHP....
>
> showReleases("releases/releases.xml", $_appFormal);
> works fine.
>
> Andras
Oops. What will not work is... 
showReleases("releases/releases.xml", $appName=$_appFormal);

I don't understand the comment about this being kdewebdev.org specific? That's 
what we're building. The question is whether we want to make it easier for 
people on our site or add things to remember for some other reason? Having a 
value that is automatically available in an application subdomain should 
minimize the requirement to call it since it will be there.

In this case I pulled CVS this morning and found an error on KLinkStatus in 
the release area showing on the page. The error was that a required parameter 
for the function was missing. It seems a good idea that if we add parameters 
to functions that may be in use they should have a default value if possible 
so as not to create errors, or we need to search out each instance of the 
function call in CVS and update it.

There are several ways to address the portability if that is what you want. My 
concern is that I want to make sure that any central library is as dead 
simple as possible to use. I'm on the second day of debugging elements of the 
order system on my site which have evolved through various methods to absurd 
levels of complexity in spite of efforts to modularize and simplify. I'm 
probably paranoid about this.
-- 
Eric Laffoon
Project Lead - kdewebdev module


More information about the kdewebdev-site mailing list