On Thu, 2008-09-25 at 23:02 -0400, Robert Cummings wrote:
> On Fri, 2008-09-26 at 02:10 +0200, Jochem Maas wrote:
> > Ashley Sheridan schreef:
> > > On Fri, 2008-09-26 at 01:05 +0200, Jochem Maas wrote:
> > >> tedd schreef:
> > >>> At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
> > Seems kin
On Fri, 2008-09-26 at 02:10 +0200, Jochem Maas wrote:
> Ashley Sheridan schreef:
> > On Fri, 2008-09-26 at 01:05 +0200, Jochem Maas wrote:
> >> tedd schreef:
> >>> At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
> Seems kind of silly to have every function in it's own file. Also seems
>
On Fri, 2008-09-26 at 01:05 +0200, Jochem Maas wrote:
> tedd schreef:
> > At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
> >> Seems kind of silly to have every function in it's own file. Also seems
> >> kind of cluttered ot have every function in one file.
> >>
> >> Now grouping related functions
Ashley Sheridan schreef:
> On Fri, 2008-09-26 at 01:05 +0200, Jochem Maas wrote:
>> tedd schreef:
>>> At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
Seems kind of silly to have every function in it's own file. Also seems
kind of cluttered ot have every function in one file.
No
On Fri, 2008-09-26 at 01:05 +0200, Jochem Maas wrote:
> tedd schreef:
> > At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
> >> Seems kind of silly to have every function in it's own file. Also seems
> >> kind of cluttered ot have every function in one file.
> >>
> >> Now grouping related functions
tedd schreef:
> At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
>> Seems kind of silly to have every function in it's own file. Also seems
>> kind of cluttered ot have every function in one file.
>>
>> Now grouping related functions into a single file... that's sounds like
>> a good middle ground.
At 3:44 PM -0400 9/24/08, Robert Cummings wrote:
Seems kind of silly to have every function in it's own file. Also seems
kind of cluttered ot have every function in one file.
Now grouping related functions into a single file... that's sounds like
a good middle ground.
Cheers,
Rob.
The Goldie
On Wed, 2008-09-24 at 13:58 -0500, Richard Lynch wrote:
> > -Original Message-
> > Right now I use one file, usually called functions.php, with all
> > functions I'm going to use most likely on every page.
> > Then, I create each function I'm going to use once in a while as
> > separate fil
> -Original Message-
> Right now I use one file, usually called functions.php, with all
> functions I'm going to use most likely on every page.
> Then, I create each function I'm going to use once in a while as
> separate file.
> Pro: I would include a function when I'm going to use.
> Con:
On Wed, 2008-09-24 at 20:32 +0300, Thodoris wrote:
>
> > On Wed, 2008-09-24 at 12:37 -0400, b wrote:
> >
> > > Lamp Lists wrote:
> > >
> > > > Hi,
> > > > Right now I use one file, usually called functions.php, with all
> > > > functions I'm going to use most likely on every page.
> > > >
On Wed, 2008-09-24 at 12:37 -0400, b wrote:
Lamp Lists wrote:
Hi,
Right now I use one file, usually called functions.php, with all functions I'm
going to use most likely on every page.
Then, I create each function I'm going to use once in a while as separate file.
Pro: I would include
On Wed, Sep 24, 2008 at 12:28 PM, Lamp Lists <[EMAIL PROTECTED]> wrote:
> Hi,
> Right now I use one file, usually called functions.php, with all functions
> I'm going to use most likely on every page.
> Then, I create each function I'm going to use once in a while as separate
> file.
> Pro: I wou
Ashley Sheridan wrote:
On Wed, 2008-09-24 at 12:37 -0400, b wrote:
Lamp Lists wrote:
Hi, Right now I use one file, usually called functions.php, with
all functions I'm going to use most likely on every page. Then, I
create each function I'm going to use once in a while as separate
file. Pro: I
On Wed, 2008-09-24 at 12:37 -0400, b wrote:
> Lamp Lists wrote:
> > Hi,
> > Right now I use one file, usually called functions.php, with all functions
> > I'm going to use most likely on every page.
> > Then, I create each function I'm going to use once in a while as separate
> > file.
> > Pro: I
Lamp Lists wrote:
Hi,
Right now I use one file, usually called functions.php, with all functions I'm
going to use most likely on every page.
Then, I create each function I'm going to use once in a while as separate file.
Pro: I would include a function when I'm going to use.
Con: I have to write
On Sun, August 26, 2007 12:46 am, Robert Keizer wrote:
> I am currently working on a module testing class, I can't seem to find
> the
> correct syntax. Here is an example of the problem:
>
> function foo( $var ){
> include $var.'.php';
> return $var(); //
I tested this functionality.
This is working fine.
foo.php
somefunction.php
Out put is hello.
You make sure that your both files are in same folder and make sure that
$var.'.php' is exist with $var function.
Warm Regards,
Sanjeev
http://www.sanchanworld.com/
http://webdirector
On Sat, 2007-08-25 at 23:46 -0600, Robert Keizer wrote:
> I am currently working on a module testing class, I can't seem to find the
> correct syntax. Here is an example of the problem:
>
> function foo( $var ){
> include $var.'.php';
> return $var(); //
my form action usually looks like this
some.php?action=update&ID=1
my update will look like update table set *** where _rowid=$_GET['ID']
so therefore its globally used. i'd use the id from the get var
but i guess in the delete function i could place this within the update
action so
case 'upda
[EMAIL PROTECTED] wrote:
apologies i generally use this system for deleting records, i give a
confirm box if they press ok it goes to another action, i suppose i should
change this system to submit the form instead and check for the post var ?
i guess at least it could store the http_referer then
apologies i generally use this system for deleting records, i give a
confirm box if they press ok it goes to another action, i suppose i should
change this system to submit the form instead and check for the post var ?
i guess at least it could store the http_referer then :\
> [EMAIL PROTECTED] wr
[EMAIL PROTECTED] wrote:
>>Dan J. Rychlik wrote:
>>>Is their an easy way to call a function based upon a button action?
>>
>>Example:
>>
>>
>>
>>
>>
>>
>>action.php:
>>function action1() {
>>echo "Hello, I'm action1";
>>}
>>
>>
>>function action2() {
>>echo "Hello, I'm action2";
>>}
wont they both be set ?
i generally use a button type and onclick document.location.href to enforce
an action in the get variable like something.php?action=something
> Example:
>
>
>
>
>
>
> action.php:
> function action1() {
> echo "Hello, I'm action1";
> }
>
>
> function action2() {
>
Example:
action.php:
function action1() {
echo "Hello, I'm action1";
}
function action2() {
echo "Hello, I'm action2";
}
if(isset($_GET['action1'])) {
action1();
}
if(isset($_GET['action2'])) {
action2();
}
Dan J. Rychlik wrote:
Is their an easy way to call a fu
this helps,
Warren Vail
-Original Message-
From: Robert Cummings [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 3:36 PM
To: Dan J. Rychlik
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] Calling functions from Button actions
Any form system (I'm guessing, but I only use my ow
Any form system (I'm guessing, but I only use my own so I could be
mistaken) that allows custom validation should enable trivial function
calling based on a button click.
Cheers,
Rob.
On Fri, 2003-09-12 at 18:29, Dan J. Rychlik wrote:
> Is their an easy way to call a function based upon a button
Hello
What you are asking isn't possible that way.
You have to write a controller script that calls the appropriate functions
on your object.
Example:
controller.php is the controller script
A link on your page:
Some Action
In controller.php you do something like:
You might also want to loo
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 24, 2003 12:20 PM
To: Daniel Rychlik; [EMAIL PROTECTED]
Subject: Re: [PHP] calling functions in classes using text and graphic
links
I am not sure what you mean but if you are trying to call functions that
exist within your class
you need to do something
I am not sure what you mean but if you are trying to call functions that
exist within your class
you need to do something like the following
$fg = new YourClass.class.php;
$fg->yourfunctionname($arguements);
- Original Message -
From: "Daniel Rychlik" <[EMAIL PROTECTED]>
To: <[EMAIL PROT
On Fri, 13 Apr 2001, Rasmus Lerdorf wrote:
>If a function has not been defined to take optional arguments, then you
>*must* provide these arguments when you call the function. The fact that
>previous versions of PHP incorrectly let you do this was at best an
>undocumented misfeature, but more li
If a function has not been defined to take optional arguments, then you
*must* provide these arguments when you call the function. The fact that
previous versions of PHP incorrectly let you do this was at best an
undocumented misfeature, but more likely a bug.
And yes, having optional arguments
On Fri, 13 Apr 2001, Hardy Merrill wrote:
>I found the same problem - when we upgraded to PHP4, function calls
>that used to work and NOT provide all the parameters, started failing.
>
>The way I fixed it was to give each parameter a default value *IN*
>the function definition, like:
>
>function
Chris Aitken [[EMAIL PROTECTED]] wrote:
> On Fri, 13 Apr 2001, Chris Aitken wrote:
>
> >---
> >
> >Warning: Missing argument 2 for stripe() in /location/to/included/file.php on line
>257
> >Warning: Missing argument 3 for stripe() in /location/to/included/file
> Can i call a function from the action line of a form?
No, since the tag needs to point to a receiving PHP script.
PHP code is executed on the server side, not the browser.
PHP code is executed on the server side, not the browser.
PHP code is executed on the server side, not the browser.
PHP c
34 matches
Mail list logo
