Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #15988
| From | James Harris <james.harris.1@gmail.com> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: PHP boilerplate to appear at the top of any program |
| Date | 2015-12-26 10:09 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <n5losu$711$1@dont-email.me> (permalink) |
| References | (3 earlier) <n56dvt$eht$1@jstuckle.eternal-september.org> <n56nbb$ide$1@dont-email.me> <n5777c$ju2$1@jstuckle.eternal-september.org> <n5jopt$ou8$1@dont-email.me> <n5jqdp$u90$1@jstuckle.eternal-september.org> |
On 25/12/2015 16:23, Jerry Stuckle wrote:
> On 12/25/2015 10:56 AM, James Harris wrote:
>> On 20/12/2015 21:42, Jerry Stuckle wrote:
...
There are at least two aspects to this and it is important to
distinguish them.
1. The settings in each php.ini file
2. Resources which are external to the PHP program
IMO it should be possible to write one program and have it work in many
different environments, each of which has its own php.ini file.
The program should also be robust enough correctly to handle the absence
or loss of any external resources.
I mention that distinction at the start of this reply in case you are
thinking just about the ini file.
>>> It's not your responsibility to determine what other peoples'
>>> php.ini files are set to.
>>
>> I did not propose setting someone else's php.ini, only overriding
>> select few values if needed for a specific program so that that
>> program can execute with certain guarantees. You are used to
>> controlling the php.ini file which could have led you to always
>> trusting every single one of its settings.
>>
>
> Which is exactly what you should NOT do. I didn't say you should
> change their php.ini. I said you shouldn't override the settings
> they want. It is their system, not yours.
Are you saying that of the 500 or so currently defined php.ini settings
there are none that you would ever want to override, not even one? Do
you really know the 500+ settings that well? I don't.
And what about php.ini settings that might be added in future versions
of PHP? Are you saying you know now that you would never want to
override any of them, even without yet knowing what they will be? That
seems unreasonable to me.
More importantly, consider that you want your PHP program to run,
completely unchanged, in many different environments. They could be your
test environment(s) and many different potential production
environments. Don't get me wrong. I think I would trust the vast
majority of the ini file settings of those environments. But without
knowing what they all are I am not prepared to give them carte-blanche -
which is why I was asking about overriding certain such settings.
>>>> A simple example is the page title. Consider emitting
>>>>
>>>> <title>T</title>
>>>>
>>>> There is to be a certain title, T, if everything is normal and
>>>> a different title if something goes wrong. I cannot produce
>>>> that line or anything after it (which essentially includes all
>>>> the page content) until I know whether there are any errors or
>>>> not. (Such errors are not from bugs but from runtime issues
>>>> such as absence of resources.)
>>>>
>>>> Since you object to what I am doing what would you do for such
>>>> a title problem?
>>>>
>>>
>>> Exactly what errors are you talking about?
>>
>> That would depend on the needs of a specific program. Remember, I
>> was asking about an approach that would be valid for general PHP
>> programming rather than something specific. Basically, such errors
>> would be any which meant that the page designer wanted to result in
>> a different title. Such errors would include any resources that the
>> page needed which might be external to the PHP program.
>>
>
> Not overriding any php.ini settings is valid for general PHP
> programming. If you want to change things, the code your page
> appropriately.
You may be mixing two things up. The ini file was discussed above. This
part of the discussion is not about ini file settings but about being
able to set a page's title only once certain resources (such as the
contents of files and databases) are known to be present and correct.
You didn't answer the question which was: as you don't like my idea of
storing or buffering data before generating the title, what would you do
so that the title can differ depending on what resources are available?
I am aware that the title could be changed in JavaScript but that would
only work in browsers where JavaScript is enabled. So the only
guaranteed approach I can see is to hold on to the critical data until
all checks have been completed.
>>>>>>>> I have code such as the above at the moment but for
>>>>>>>> various reasons it is not completely satisfactory. I
>>>>>>>> wondered if people who were more familiar with PHP had
>>>>>>>> come up with a better approach.
>>>>>>>>
>>>>>>>
>>>>>>> Probably because it's a bad idea.
>>>>>>
>>>>>> I don't think it's a bad idea to have some initial setup
>>>>>> code, for the reasons mentioned above. My main problem is
>>>>>> currently having to replicate too much at the top of each
>>>>>> program.
>>>>>>
>>>>>
>>>>> That's because you're not using good programming practices.
>>>>
>>>> In your opinion, you mean. In fact, I am probably writing code
>>>> that is more robust than you are used to.... :-)
>>>>
>>>
>>> After 47 years of writing code in close to 20 languages
>>> (including 13 years with IBM), I doubt it very much.
>>
>> Well, my comment was somewhat tongue-in-cheek but time programming
>> doesn't correlate with attitude to robustness. That is especially
>> true for you as you are used to completely controlling the
>> environment in which your PHP scripts run.
>>
>
> The point is - you are NOT writing robust code. In fact, your code
> is less robust than what most people write, because they don't need
> to override php.ini settings.
Nonsense! The whole point of this discussion is about making code robust.
I spoke about overriding certain ini settings so that the code would be
robust enough to handle different environments.
I spoke about error checking before generating output so that the code
would be robust enough to cope with absence or loss of external resources.
You keep talking about php.ini settings but that is discussed at the
top. The main part of this discussion, including the part above, is more
about checking that all necessary resources are present before
generating a "success page" AND ensuring that data from those resources
are still available when we come to generate the contents of the page.
The title issue, above, is an excellent example showing that we cannot
always start generating HTML until we have carried out checks and cached
necessary data. From what you have said, you expect a page to depend on
only one resource (if it's present you start to generate output) and if
that resource fails partway through you say it is such a remote chance
that it's not worth programming for. I would call your assumptions LESS
robust than mine.
>>>>> What do you have in the preamble, anyway?
>>>>
>>>> At the moment, aside from the ini_sets above, basically the
>>>> same as you tell me you have, below. If you don't like what I
>>>> have then you are also criticising yourself.
>>>>
>>>
>>> No, I'm telling you I don't have a preamble. I include classes
>>> I've developed myself, where necessary. I include userid's and
>>> passwords to databases. But I don't include any ini_set(),
>>> ob_start() or any other garbage code.
>>
>> I would call any standard includes a preamble.
>>
>
> I didn't say I had a "standard include". I said I include classes
> that and userids/passwords that *are needed*. Each page has
> different needs, and generally includes different classes.
>
> A class file is *not* a "preamble". Neither is a file containing
> userids and passwords.
Well, I would regard a common statement which includes a class file to
be a preamble, or part of one. I was asking about something to put at
the top of every PHP file. That could be a single include, if that would do.
>>>>>> How about the following as an approach?
>>>>>>
>>>>>> require("code_preamble_XXX"); (Where XXX is dev or prod)
>>>>>>
>>>>>> and then call certain functions from the code_preamble with
>>>>>> parameters to customise their effects as necessary.
>>>>>>
>>>>>
>>>>> Again, exactly what are you doing in the preamble that's
>>>>> required on every page?
>>>>
>>>> This is not about page content such as headers, sidebars,
>>>> footers etc. That's a separate issue. This is purely about
>>>> setup for PHP programming.
>>>>
>>>
>>> You're not answering my question.
>>
>> Well, this thread was there to ask for specifics but it could
>> include environment settings, common utility routines, debugging
>> routines if developing, common classes, database access parameters
>> etc.
>>
>
> I have answered your question multiple times. But you aren't
> listening.
There's a difference between listening and agreeing. I have listened to
what you have said. I even took on board your point about buffering and
have changed my approach. But I don't agree with everything you say.
That's a disagreement, not a failure to listen. The two are very
different things. Just because someone disagrees with you does not mean
he is not listening.
> Include what the script needs - nothing more, nothing
> less. And don't change the user's php.ini settings.
You keep answering about the php.ini file but that was dealt with at the
top.
Are you saying that there is NOTHING that you would include at the top
of every PHP file? Not even one include? What about a single include
which would pull in info or set settings relevant to the environment?
For example
require_once "current_env.php";
The idea of that would be to set settings relevant to the environment in
which the PHP script is to run. There might be many current_env.php
files, one for each environment, but all of them would set up things
needed for the including PHP program to run properly.
Any good?
>>>>> I told you what I put in such a preamble - nothing other than
>>>>> common classes which I've developed and userids/passwords.
>>>>> And I haven't, for around 15 years of PHP programming and
>>>>> thousands of PHP pages. I don't need them because I use good
>>>>> programing practices instead of snarky work-arounds which
>>>>> cause more problems in the long run.
>>>>
>>>> It sounds like you do what you are complaining about me
>>>> suggesting...!
>>>>
>>>> James
>>>>
>>>
>>> Not at all. Common classes are reusable code (i.e. database
>>> access classes). Userids and passwords should NEVER be in a file
>>> that's in the server's DOCUMENT_ROOT.
>>
>> I did not say that the stuff included had to be under the
>> DOCUMENT_ROOT.
>>
>> James
>>
>
> *I* said the userids and passwords should *not* be under the
> DOCUMENT_ROOT.
I know. As with elsewhere in this thread you seem to object to the
places where I expressed agreement with you.
James
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
PHP boilerplate to appear at the top of any program James Harris <james.harris.1@gmail.com> - 2015-12-19 10:03 +0000
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-19 08:20 -0500
Re: PHP boilerplate to appear at the top of any program James Harris <james.harris.1@gmail.com> - 2015-12-20 10:16 +0000
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-20 09:31 -0500
Re: PHP boilerplate to appear at the top of any program James Harris <james.harris.1@gmail.com> - 2015-12-20 17:11 +0000
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-20 16:42 -0500
Re: PHP boilerplate to appear at the top of any program James Harris <james.harris.1@gmail.com> - 2015-12-25 15:56 +0000
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-25 11:23 -0500
Re: PHP boilerplate to appear at the top of any program James Harris <james.harris.1@gmail.com> - 2015-12-26 10:09 +0000
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-26 09:33 -0500
Re: PHP boilerplate to appear at the top of any program Denis McMahon <denismfmcmahon@gmail.com> - 2015-12-20 22:54 +0000
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-20 18:40 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 10:38 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 08:41 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 15:30 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 11:04 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 23:24 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 19:16 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 00:33 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 19:19 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 10:27 +0100
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-22 11:18 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 06:34 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-22 16:00 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 10:56 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-22 15:56 +0100
OT: pre-PHP day (was: PHP boilerplate to appear at the top of any program) Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 16:57 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 11:03 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-22 18:02 +0100
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-22 14:47 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 11:04 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-22 18:22 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 12:33 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-22 18:46 +0100
Re: PHP boilerplate to appear at the top of any program "Christoph M. Becker" <cmbecker69@arcor.de> - 2015-12-21 17:25 +0100
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-21 23:17 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 19:23 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-28 15:26 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-28 10:02 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-28 18:14 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-28 12:29 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-28 18:54 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-28 14:15 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-28 21:18 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-28 15:49 -0500
Re: PHP boilerplate to appear at the top of any program Richard Damon <Richard@Damon-Family.org> - 2015-12-28 20:31 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-28 20:48 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-30 11:26 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 12:33 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-30 18:57 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 15:14 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-30 19:05 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 15:18 -0500
Re: PHP boilerplate to appear at the top of any program Richard Damon <Richard@Damon-Family.org> - 2015-12-30 21:55 -0500
Re: PHP boilerplate to appear at the top of any program Matthew Carter <m@ahungry.com> - 2015-12-30 22:14 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 22:43 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 22:46 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 22:42 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 09:07 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 07:47 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 16:11 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 10:47 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 17:43 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 13:49 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 20:35 +0100
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-30 11:18 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 12:36 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-30 19:09 +0100
Re: PHP boilerplate to appear at the top of any program Thomas Mlynarczyk <thomas@mlynarczyk-webdesign.de> - 2015-12-30 20:28 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 15:21 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 09:09 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-30 15:21 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 09:16 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 07:53 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 16:03 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 10:49 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-31 17:16 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 13:54 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-31 20:41 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 14:47 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 20:56 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 15:21 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-31 17:52 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-31 13:51 -0500
Re: PHP boilerplate to appear at the top of any program Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-12-28 19:35 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-28 14:17 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 00:20 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 19:27 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 10:12 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 06:36 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 13:57 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 11:05 -0500
Re: PHP boilerplate to appear at the top of any program Gregor Kofler <usenet@gregorkofler.com> - 2015-12-22 17:22 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 12:01 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2015-12-22 18:25 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 12:34 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2015-12-21 14:53 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 19:30 -0500
Re: PHP boilerplate to appear at the top of any program Matthew Carter <m@ahungry.com> - 2015-12-21 21:40 -0500
Re: PHP boilerplate to appear at the top of any program Matthew Carter <m@ahungry.com> - 2015-12-21 21:47 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 21:55 -0500
Re: PHP boilerplate to appear at the top of any program Matthew Carter <m@ahungry.com> - 2015-12-21 21:57 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 22:01 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-21 21:54 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2015-12-22 11:54 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 15:42 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-02 11:08 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-02 15:12 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-04 10:41 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 14:39 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2015-12-22 11:49 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2015-12-22 15:44 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-02 11:09 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-02 15:14 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-04 10:42 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 14:41 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-04 22:54 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 19:40 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 04:19 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 22:29 -0500
Re: PHP boilerplate to appear at the top of any program Matthew Carter <m@ahungry.com> - 2016-01-05 02:02 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 09:08 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 18:55 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 14:06 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-04 15:51 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 19:41 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 04:27 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 22:31 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 04:48 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-04 22:52 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 09:16 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 09:08 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 18:59 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 14:07 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-06 01:13 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 20:52 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-06 08:53 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-06 09:15 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-05 09:00 -0800
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-05 19:01 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 14:09 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-06 01:15 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 20:51 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-06 08:54 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-06 09:16 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-11 09:02 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-11 08:02 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-11 23:42 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-11 20:44 -0500
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-05 14:09 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-06 09:27 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-06 15:25 -0500
Re: PHP boilerplate to appear at the top of any program Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2016-01-06 13:27 -0800
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-06 16:32 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-11 09:03 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-11 08:03 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-11 23:45 +0100
Re: PHP boilerplate to appear at the top of any program Jerry Stuckle <jstucklex@attglobal.net> - 2016-01-11 20:48 -0500
Re: PHP boilerplate to appear at the top of any program Arno Welzel <usenet@arnowelzel.de> - 2016-01-12 05:34 +0100
csiph-web