At 12:05 PM -0500 3/4/08, Daniel Brown wrote:
No, that would work fine in any case. In fact, code should always
be thoroughly tested before going into production.
Yeah, but that rules out all the fun.
Cheers,
tedd
--
---
http://sperling.com http://ancientstones.com http://earthsto
On Tue, Mar 4, 2008 at 11:29 AM, Mike Potter <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 29, 2008 at 2:25 PM, Daniel Brown wrote:
> > On Thu, Feb 28, 2008 at 9:58 PM, Richard S. Crawford
> > > I'm trying to figure out a way to make sure an included PHP file has no
> > > syntax
> > > errors before
At 7:52 PM + 2/29/08, Richard Heyes wrote:
1. My host does not allow command line access and has disabled shell
execution of PHP;
2. Error reporting has been turned off and I can't seem to turn that on
with ini_set or error_reporting (which is fun when I have minor syntax
errors to fix); a
At 6:58 PM -0800 2/28/08, Richard S. Crawford wrote:
I'm trying to figure out a way to make sure an included PHP file has no syntax
errors before actually including it as a part of project. Is this even
possible? I'm running into brick walls.
I'm not sure if this is what you are asking for, bu
On Thu, February 28, 2008 10:25 pm, Robert Cummings wrote:
> Doh! Time for me to start trawling the PHP site again to acquaint
> myself
> with all the new functions :) I probably would have found it though if
> searching the site's functions for syntax didn't take me directly to
> the
> documentati
Aschwin Wesselius wrote:
Chris wrote:
have you considered installing a local copy of php (and suitable
webserver)
so you can test it there?
I'd also suggest using a revision control system (subversion or git)
and have pre-commit hooks to check the syntax.
It's a bit of work to set up but
Chris wrote:
have you considered installing a local copy of php (and suitable
webserver)
so you can test it there?
I'd also suggest using a revision control system (subversion or git)
and have pre-commit hooks to check the syntax.
It's a bit of work to set up but once it's done you'll not
have you considered installing a local copy of php (and suitable webserver)
so you can test it there?
I'd also suggest using a revision control system (subversion or git) and
have pre-commit hooks to check the syntax.
It's a bit of work to set up but once it's done you'll notice a
differen
On Fri, Feb 29, 2008 at 10:02 PM, Richard S. Crawford
<[EMAIL PROTECTED]> wrote:
> On Friday 29 February 2008 11:58:16 Daniel Brown wrote:
> > Get a new host that knows how to administer a web server. PHP 4.3
> > was released 27 December, 2002, with the latest from the 4.3 branch
> > (4.3.1
On Friday 29 February 2008 11:58:16 Daniel Brown wrote:
> Get a new host that knows how to administer a web server. PHP 4.3
> was released 27 December, 2002, with the latest from the 4.3 branch
> (4.3.11) being released 31 March, 2005. The CHANGELOG should give you
> an idea of how *horrible*
On Fri, Feb 29, 2008 at 3:42 PM, Jochem Maas <[EMAIL PROTECTED]> wrote:
> have you considered installing a local copy of php (and suitable webserver)
> so you can test it there?
Always good advice. At the very least, a remote dev box on which
to work the code. However, it's not going to be
Richard S. Crawford schreef:
Thanks to everyone for the suggestions. Unfortunately, I'm up against a
couple of major hurdles:
1. My host does not allow command line access and has disabled shell
execution of PHP;
2. Error reporting has been turned off and I can't seem to turn that on
with in
On Fri, Feb 29, 2008 at 2:32 PM, Richard S. Crawford
<[EMAIL PROTECTED]> wrote:
> Thanks to everyone for the suggestions. Unfortunately, I'm up against a
> couple of major hurdles:
Not to be a smartass with my responses here
> 1. My host does not allow command line access and has disabl
1. My host does not allow command line access and has disabled shell
execution of PHP;
2. Error reporting has been turned off and I can't seem to turn that on
with ini_set or error_reporting (which is fun when I have minor syntax
errors to fix); and
3. My host is also stuck in PHP 4.3, so the
Thanks to everyone for the suggestions. Unfortunately, I'm up against a
couple of major hurdles:
1. My host does not allow command line access and has disabled shell
execution of PHP;
2. Error reporting has been turned off and I can't seem to turn that on
with ini_set or error_reporting (which
De: Daniel Brown [mailto:[EMAIL PROTECTED]
On Thu, Feb 28, 2008 at 9:58 PM, Richard S. Crawford
<[EMAIL PROTECTED]> wrote:
> I'm trying to figure out a way to make sure an included PHP file has
> no syntax errors before actually including it as a part of project.
> Is this even possible? I'
On Thu, Feb 28, 2008 at 9:58 PM, Richard S. Crawford
<[EMAIL PROTECTED]> wrote:
> I'm trying to figure out a way to make sure an included PHP file has no syntax
> errors before actually including it as a part of project. Is this even
> possible? I'm running into brick walls.
As far as I kno
On Thu, 2008-02-28 at 20:53 -0800, Jim Lucas wrote:
> Robert Cummings wrote:
> > On Thu, 2008-02-28 at 20:46 -0800, Jim Lucas wrote:
> >> Robert Cummings wrote:
> >>> On Thu, 2008-02-28 at 20:17 -0800, Casey wrote:
> On Thu, Feb 28, 2008 at 7:50 PM, Robert Cummings <[EMAIL PROTECTED]>
>
Robert Cummings wrote:
On Thu, 2008-02-28 at 20:46 -0800, Jim Lucas wrote:
Robert Cummings wrote:
On Thu, 2008-02-28 at 20:17 -0800, Casey wrote:
On Thu, Feb 28, 2008 at 7:50 PM, Robert Cummings <[EMAIL PROTECTED]> wrote:
On Thu, 2008-02-28 at 18:58 -0800, Richard S. Crawford wrote:
> I'm t
On Thu, 2008-02-28 at 20:46 -0800, Jim Lucas wrote:
> Robert Cummings wrote:
> > On Thu, 2008-02-28 at 20:17 -0800, Casey wrote:
> >> On Thu, Feb 28, 2008 at 7:50 PM, Robert Cummings <[EMAIL PROTECTED]> wrote:
> >>> On Thu, 2008-02-28 at 18:58 -0800, Richard S. Crawford wrote:
> >>> > I'm trying
Robert Cummings wrote:
On Thu, 2008-02-28 at 20:17 -0800, Casey wrote:
On Thu, Feb 28, 2008 at 7:50 PM, Robert Cummings <[EMAIL PROTECTED]> wrote:
On Thu, 2008-02-28 at 18:58 -0800, Richard S. Crawford wrote:
> I'm trying to figure out a way to make sure an included PHP file has no
syntax
>
On Thu, 2008-02-28 at 20:17 -0800, Casey wrote:
> On Thu, Feb 28, 2008 at 7:50 PM, Robert Cummings <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, 2008-02-28 at 18:58 -0800, Richard S. Crawford wrote:
> > > I'm trying to figure out a way to make sure an included PHP file has no
> > syntax
> > > err
On Thu, Feb 28, 2008 at 7:50 PM, Robert Cummings <[EMAIL PROTECTED]> wrote:
>
> On Thu, 2008-02-28 at 18:58 -0800, Richard S. Crawford wrote:
> > I'm trying to figure out a way to make sure an included PHP file has no
> syntax
> > errors before actually including it as a part of project. Is thi
On Thu, 2008-02-28 at 18:58 -0800, Richard S. Crawford wrote:
> I'm trying to figure out a way to make sure an included PHP file has no
> syntax
> errors before actually including it as a part of project. Is this even
> possible? I'm running into brick walls.
I don't believe there is a functi
On Thu, Feb 28, 2008 at 9:58 PM, Richard S. Crawford <
[EMAIL PROTECTED]> wrote:
> I'm trying to figure out a way to make sure an included PHP file has no
> syntax
> errors before actually including it as a part of project. Is this even
> possible? I'm running into brick walls.
>
>
The include i
I'm trying to figure out a way to make sure an included PHP file has no syntax
errors before actually including it as a part of project. Is this even
possible? I'm running into brick walls.
--
Slainte,
Richard S. Crawford
Editor-in-chief, Daikaijuzine (http://www.daikaijuzine.com)
Personal web
26 matches
Mail list logo
