php-general-digest-helplists.php.net
Date: Fri Sep 22 2006 - 06:35:08 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

php-general Digest 22 Sep 2006 11:35:08 -0000 Issue 4361

Topics (messages 242041 through 242060):

web browser shows blank page when accessing *.php file
        242041 by: Anna Barnes
        242044 by: Martin Marques
        242048 by: Curt Zirzow
        242049 by: Anna Barnes
        242053 by: Curt Zirzow

+AFs-OT+AF0- Working with version control
        242042 by: Chris W. Parker
        242043 by: Brad Bonkoski
        242045 by: tedd
        242046 by: Robert Cummings
        242047 by: Colin Guthrie

Help converting C to PHP
        242050 by: Tom Atkinson
        242051 by: Kevin Waterson
        242052 by: Tom Atkinson
        242054 by: Curt Zirzow
        242055 by: Curt Zirzow
        242056 by: Kevin Waterson
        242057 by: Tom Atkinson
        242058 by: Christopher Watson
        242059 by: Tom Atkinson

Re: Frustrated trying to get help from your site
        242060 by: Arno Kuhl

Administrivia:

To subscribe to the digest, e-mail:
        php-general-digest-subscribelists.php.net

To unsubscribe from the digest, e-mail:
        php-general-digest-unsubscribelists.php.net

To post to the list, e-mail:
        php-generallists.php.net

----------------------------------------------------------------------

attached mail follows:

We are publishing an ical calendar from a mac on a webserver running
apache on solaris 8. However, its suddenly stopped working via
webrowser. I have tried to stop and start the httpd to get it going
again but to no avail.

when I access through safari or explorer on OSX.4 the access_log file
says

mac-abarnes.fmri.columbia.edu - abarnes [19/Sep/2006:15:51:47 -0400]
"GET / HTTP/1.1" 302 5
mac-abarnes.fmri.columbia.edu - abarnes [19/Sep/2006:15:52:47 -0400]
"GET /week.php HTTP/1.1" 200 5

and the error_log file says

[Tue Sep 19 15:53:57 2006] [error] PHP Fatal error: Maximum execution
time of 60 seconds exceeded in /websites/ical/functions/
ical_parser.php on line 494

Not quite sure where to go from here.

thanks
Anna
http://ical.fmri.columbia.edu/week.php

attached mail follows:

On Thu, 21 Sep 2006 17:13:44 -0400, Anna Barnes <ab2540columbia.edu> wrote:
>
> and the error_log file says
>
> [Tue Sep 19 15:53:57 2006] [error] PHP Fatal error: Maximum execution
> time of 60 seconds exceeded in /websites/ical/functions/
> ical_parser.php on line 494

What is there in line 494 of ical_parser.php?

--
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
    del Litoral | Administrador
---------------------------------------------------------

attached mail follows:

On 9/21/06, Anna Barnes <ab2540columbia.edu> wrote:
> We are publishing an ical calendar from a mac on a webserver running
> apache on solaris 8. However, its suddenly stopped working via
> webrowser. I have tried to stop and start the httpd to get it going
> again but to no avail.
>
> when I access through safari or explorer on OSX.4 the access_log file
> says

You are being rather specific to browsers, so does this mean this
behaviour doesn't happen when you use Firefox on OSX or IE/FF on
windows?

>
> mac-abarnes.fmri.columbia.edu - abarnes [19/Sep/2006:15:51:47 -0400]
> "GET / HTTP/1.1" 302 5
> mac-abarnes.fmri.columbia.edu - abarnes [19/Sep/2006:15:52:47 -0400]
> "GET /week.php HTTP/1.1" 200 5
>
> and the error_log file says
>
> [Tue Sep 19 15:53:57 2006] [error] PHP Fatal error: Maximum execution
> time of 60 seconds exceeded in /websites/ical/functions/
> ical_parser.php on line 494
>
> Not quite sure where to go from here.

As mentioned, you need to evaluate what line 494 is actually doing..
is this a loop of some sort that is causing the max execution timeout?

Is there a browser specific thing that causes the line 494 to timeout.

What exactly is going on in the 494 area of ical_parser.php

>
> thanks
> Anna
> http://ical.fmri.columbia.edu/week.php

btw, your signature url doesnt work without a proper username and password.

Curt

attached mail follows:

Hi Curt and Martin,
Thanks for getting back to me. I'll take a look at the exact line 474
tomorrow. The reason I didn't mention it specifically is that it's only
suddenly stopped working and nothing in that code has changed.

It doesn't work in any browser, netscape, IE, firefox etc on Solaris9 or
WindowsXP

The 'signature url' is actually the calendar function that doesn't work.
I wanted to know if it works outside our LAN. What's weird is that it
asks for the username and password, it authenticates but then won't load
the page.

kindest regards
Anna

Curt Zirzow wrote:

> On 9/21/06, Anna Barnes <ab2540columbia.edu> wrote:
>
>> We are publishing an ical calendar from a mac on a webserver running
>> apache on solaris 8. However, its suddenly stopped working via
>> webrowser. I have tried to stop and start the httpd to get it going
>> again but to no avail.
>>
>> when I access through safari or explorer on OSX.4 the access_log file
>> says
>
>
> You are being rather specific to browsers, so does this mean this
> behaviour doesn't happen when you use Firefox on OSX or IE/FF on
> windows?
>
>>
>> mac-abarnes.fmri.columbia.edu - abarnes [19/Sep/2006:15:51:47 -0400]
>> "GET / HTTP/1.1" 302 5
>> mac-abarnes.fmri.columbia.edu - abarnes [19/Sep/2006:15:52:47 -0400]
>> "GET /week.php HTTP/1.1" 200 5
>>
>> and the error_log file says
>>
>> [Tue Sep 19 15:53:57 2006] [error] PHP Fatal error: Maximum execution
>> time of 60 seconds exceeded in /websites/ical/functions/
>> ical_parser.php on line 494
>>
>> Not quite sure where to go from here.
>
>
> As mentioned, you need to evaluate what line 494 is actually doing..
> is this a loop of some sort that is causing the max execution timeout?
>
> Is there a browser specific thing that causes the line 494 to timeout.
>
> What exactly is going on in the 494 area of ical_parser.php
>
>>
>> thanks
>> Anna
>> http://ical.fmri.columbia.edu/week.php
>
>
> btw, your signature url doesnt work without a proper username and
> password.
>
>
> Curt

attached mail follows:

On 9/21/06, anna barnes <ab2540columbia.edu> wrote:
> Hi Curt and Martin,
> Thanks for getting back to me. I'll take a look at the exact line 474
> tomorrow. The reason I didn't mention it specifically is that it's only
> suddenly stopped working and nothing in that code has changed.
>
> It doesn't work in any browser, netscape, IE, firefox etc on Solaris9 or
> WindowsXP

if it is happening in these cases then it is very likely a code change
or behaviou that was unexected. till we get some sor of sniplet of the
relevant code aroudn 474 it will be hard to tell wht the issue is.

>
> The 'signature url' is actually the calendar function that doesn't work.
> I wanted to know if it works outside our LAN. What's weird is that it
> asks for the username and password, it authenticates but then won't load
> the page.

This is a total seperat issue, and probably resides in the core login
method the ical system uses.

Curt/

attached mail follows:

Hello,

This is off topic but I wanted to get the list member's opinions on the
subject as it will probably benefit someone else.

Currently I don't use version control at all. What I do instead is have
one directory that contains my development website and one directory
that contains the live website which I do not directly modify. When I
need to fix something or add a new feature I edit the development site
and copy the files that I've changed.

Sometimes I will start on a new feature before I am able to finish a
previous one. This is a major problem when the features overlap and I
have to edit the same file for both features. Even if I finish one of
the features I cannot publish the files because the other feature is not
ready yet.

What I'm looking to the list for is how I can overcome this through
version control.

What I'm thinking I'd do is create a base level (say v1.0) that I then
create a branch for every new feature and then merge those things
together. The issue I see in this case is the merging.

Is this a sound strategy or should I just realize that I can't publish
until all current features enhancements are completed?

Thanks,
Chris.

attached mail follows:

Chris W. Parker wrote:
> Hello,
>
> This is off topic but I wanted to get the list member's opinions on the
> subject as it will probably benefit someone else.
>
> Currently I don't use version control at all. What I do instead is have
> one directory that contains my development website and one directory
> that contains the live website which I do not directly modify. When I
> need to fix something or add a new feature I edit the development site
> and copy the files that I've changed.
>
> Sometimes I will start on a new feature before I am able to finish a
> previous one. This is a major problem when the features overlap and I
> have to edit the same file for both features. Even if I finish one of
> the features I cannot publish the files because the other feature is not
> ready yet.
>
> What I'm looking to the list for is how I can overcome this through
> version control.
>
> What I'm thinking I'd do is create a base level (say v1.0) that I then
> create a branch for every new feature and then merge those things
> together. The issue I see in this case is the merging.
>
> Is this a sound strategy or should I just realize that I can't publish
> until all current features enhancements are completed?
>
>
> Thanks,
> Chris.
>
>
What you are currently doing would be similar if you were using source
control, only you would have the ability to revert to previous
functions, and have better logging for changes to your files.... So, I
would advocate using some source control, like subversion to make life a
little more orderly.

As for your problem... of course it is always +ACo-ideal+ACo- to complete one
branch/feature before you start a new branch/feature, but often times we
do not live in +ACo-ideal+ACo- worlds, so merging becomes a necessary evil.
source control / configuration management will not really solve this
problem, but it will provide better tools to attack the problem.

So, I would sit down and google for the Subversion Red Book and read
through some of that to get your started.
As I said before you will find some of the method similar to what you
are currently doing, it will just document your journey a little better.
-B

attached mail follows:

At 2:21 PM -0700 9/21/06, Chris W. Parker wrote:
>Hello,
>
>This is off topic but I wanted to get the list member's opinions on the
>subject as it will probably benefit someone else.
>
>-snip-
>
>Is this a sound strategy or should I just realize that I can't publish
>until all current features enhancements are completed?
>
>
>Thanks,
>Chris.

Chris:

I've been thinking about this as well. Please forgive my naiveness if
the gang already has a better way, but the method I used to do
application development was that I started with a folder that
contained all my code, which I named v1.0.

Whenever I reached a milestone of some type I thought significant, I
duplicated the entire working folder; renamed the duplicate the next
version (i.e., v1.01); and started working with the new folder. If I
screwed up, then I could always trash the new folder, duplicate the
previous version and start again. It was a system that worked for me.

At the end of the development cycle, I would have a long thread of
development versions. Often, I found that intermediate folders
provided branches for other development -- so, keeping intermediate
development versions was a plus.

Now, it's a bit different working with folders on the web because you
have one "root" (live) folder and making changes can be problematic.
However, there's enough similarity that I often follow the same
method as I used in application development.

For example, my current site http://sperling.com is alive and running
well. However, I am doing a complete rewrite of the site. As such I
duplicated the entire site and placed it in another directory,
namely: http://sperling.com/a -- and I work on that.

When I feel that revision is ready, I will save the current "root"
directory to my desktop, delete it on my server and then pull
everything out of my "a" directory and make it the new root. For me,
that would take just a few minutes. For more complex sites, where the
change must be instant, I would look into using the .htaccess file to
change the root index.

If there are better development schemes, I would like to hear about
them as well.

Cheers,

tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com

attached mail follows:

On Thu, 2006-09-21 at 18:11 -0400, tedd wrote:
> At 2:21 PM -0700 9/21/06, Chris W. Parker wrote:
> >Hello,
> >
> >This is off topic but I wanted to get the list member's opinions on the
> >subject as it will probably benefit someone else.
> >
> >-snip-
> >
> >Is this a sound strategy or should I just realize that I can't publish
> >until all current features enhancements are completed?
> >
> >
> >Thanks,
> >Chris.
>
> Chris:
>
> I've been thinking about this as well. Please forgive my naiveness if
> the gang already has a better way, but the method I used to do
> application development was that I started with a folder that
> contained all my code, which I named v1.0.
>
> Whenever I reached a milestone of some type I thought significant, I
> duplicated the entire working folder; renamed the duplicate the next
> version (i.e., v1.01); and started working with the new folder. If I
> screwed up, then I could always trash the new folder, duplicate the
> previous version and start again. It was a system that worked for me.
>
> At the end of the development cycle, I would have a long thread of
> development versions. Often, I found that intermediate folders
> provided branches for other development -- so, keeping intermediate
> development versions was a plus.
>
> Now, it's a bit different working with folders on the web because you
> have one "root" (live) folder and making changes can be problematic.
> However, there's enough similarity that I often follow the same
> method as I used in application development.
>
> For example, my current site http://sperling.com is alive and running
> well. However, I am doing a complete rewrite of the site. As such I
> duplicated the entire site and placed it in another directory,
> namely: http://sperling.com/a -- and I work on that.
>
> When I feel that revision is ready, I will save the current "root"
> directory to my desktop, delete it on my server and then pull
> everything out of my "a" directory and make it the new root. For me,
> that would take just a few minutes. For more complex sites, where the
> change must be instant, I would look into using the .htaccess file to
> change the root index.
>
> If there are better development schemes, I would like to hear about
> them as well.

Use CVS or SubVersion already. I'm not familiar with SubVersion, though
from what I hear it's has all the features of CVS. At any rate, you
create you directory, and files and stuff, add them all to the
repository. If you want a snapshot just tag the repository with a name.
This will create what you call "directory versions". At any time you can
check out the repository for a given tag, or revert a file to a given
revision, or just view changes between revision X and Y or X and Z
(skipping Y). Get in the habit of commiting your stuff often at any
given sub-milestone where you haven't broken the code. Then if you screw
up, you can retrieve any single file's revision and backup only as much
as you need. CVS also supports branching though I'm less familiar with
it. Seriously though... you have what? 4 or 5 directory clones on the
go? I can get any version of any file anywhere through 1 to 1 million
versions. You can also check out files according to date so that you
have a snapshot representative of a point in time.

Cheers,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'

attached mail follows:

Robert Cummings wrote:
> On Thu, 2006-09-21 at 18:11 -0400, tedd wrote:
>> At 2:21 PM -0700 9/21/06, Chris W. Parker wrote:
>>> Hello,
>>>
>>> This is off topic but I wanted to get the list member's opinions on the
>>> subject as it will probably benefit someone else.
>>>
>>> -snip-
>>>
>>> Is this a sound strategy or should I just realize that I can't publish
>>> until all current features enhancements are completed?
>>>
>>>
>>> Thanks,
>>> Chris.
>> Chris:
>>
>> I've been thinking about this as well. Please forgive my naiveness if
>> the gang already has a better way, but the method I used to do
>> application development was that I started with a folder that
>> contained all my code, which I named v1.0.
>>
>> Whenever I reached a milestone of some type I thought significant, I
>> duplicated the entire working folder; renamed the duplicate the next
>> version (i.e., v1.01); and started working with the new folder. If I
>> screwed up, then I could always trash the new folder, duplicate the
>> previous version and start again. It was a system that worked for me.
>>
>> At the end of the development cycle, I would have a long thread of
>> development versions. Often, I found that intermediate folders
>> provided branches for other development -- so, keeping intermediate
>> development versions was a plus.
>>
>> Now, it's a bit different working with folders on the web because you
>> have one "root" (live) folder and making changes can be problematic.
>> However, there's enough similarity that I often follow the same
>> method as I used in application development.
>>
>> For example, my current site http://sperling.com is alive and running
>> well. However, I am doing a complete rewrite of the site. As such I
>> duplicated the entire site and placed it in another directory,
>> namely: http://sperling.com/a -- and I work on that.
>>
>> When I feel that revision is ready, I will save the current "root"
>> directory to my desktop, delete it on my server and then pull
>> everything out of my "a" directory and make it the new root. For me,
>> that would take just a few minutes. For more complex sites, where the
>> change must be instant, I would look into using the .htaccess file to
>> change the root index.
>>
>> If there are better development schemes, I would like to hear about
>> them as well.
>
> Use CVS or SubVersion already. I'm not familiar with SubVersion, though
> from what I hear it's has all the features of CVS.

I would strongly recommend subversion over CVS. I've used CVS for many
years and can't believe how much better things are now I've switched to SVN.

I second Brad's recommendation of reading
http://subversion.red-bean.com/ - The Subversion Book. It makes for
excellent reading.

You can quite easily work on a "trunk" project, make multiple changes
and use it for general development work. (e.g. /trunk/myproject/)

When you are ready for your first deployment, you create a "staging"
branch (/branches/myproject/staging) using the "svn cp" command. You
then test this version in a simulated live environment. Other developers
can carry on working on /trunk/myproject while you work. If you need to
make any changes (e.g. bugs found during staging process), just commit
to the /branches/myproject/staging branch (don't worry we'll merge this
back to trunk in a bit).

Once you are happy, you are ready for the first deployment. Use "svn cp"
to create your deployment branch (e.g. /branches/myproject/deployed).
Also to keep a permanent record, you should tag this deployment (again
using "svn cp" to e.g. /tags/myproject/deployed-20060922010000).

On your production environment, just check out
/branch/myproject/deployed (you could use the tag, but it will be more
complex when updating on next deployment (it would require using "svn
switch" rather than just "svn up").

Now just merge any commits made to the staging brach back to trunk (use
"svn merge"). Now carry on development.

Now you're ready for deployment 2! This time the staging branch has
already been made so no need to use "svn cp" to create it. Just svn
merge all the changesets made to trunk since your last deployment.

Again test it and commit any required bugfixes. Then use svn merge to
apply all the changesets in the staging branch to the deployment branch
since you lasted deployed (it may just be one, but could be more if
there are bugfixes). Once you have commited these changes, make a new
tag with "svn cp" for your records (tags do not take up any real disk
space to don't worry about them even if your project is huge!)

On your production environment just run "svn up".

Oh, don't forget to merge any bugfixes made to your staging branch back
to trunk!

If in an emergency you need to roll back, just issue an "svn switch
REPO/tags/myproject/deployed-<date of previous deployment>" and you're
back to how you were.

Hope this simple process helps - read the SVN book to get a better
understanding of the terms I've used.

Col.

attached mail follows:

Hello,

I am attempting to convert this code for generating the digits of pi
from the original C (below) to PHP.

  long k=4e3,p,a[337],q,t=1e3;
   main(j){for(;a[j=q=0]+=2,--k;)
   for(p=1+2*k;j<337;q=a[j]*k+q%p*t,a[j++]=q/p)
   k!=j>2?:printf("%.3d",a[j-2]%t+q/p/t);}

I converted this to a more readable form:

long k=4e3;
int p;
int a[337];
int q;
int t=1e3;

main(j){
   for(;a[j=q=0]+=2,--k;){
     for(p=1+(2*k);j<337;q=(a[j]*k)+((q%p)*t),a[j++]=(q/p)){
       if (j>2 && k==1) printf("%.3d",(a[j-2]%t)+((q/p)/t));
     }
   }
}

and then changed it to PHP syntax

$k=4e3;
$p=0;
$a=array();
$q=0;
$t=1e3;

for(;$a[$j=$q=0]+=2,--$k;){
   for($p=1+(2*$k);$j<337;$q=($a[$j]*$k)+(($q%$p)*$t),$a[$j++]=($q/$p)){
     if ($j>2 && $k==1) printf("%.3d",($a[$j-2]%$t)+(($q/$p)/$t));
   }
}

The C code correctly gives me pi, but the PHP code gives me some other
number which is not pi.

What am I missing?

Tom.

attached mail follows:

This one time, at band camp, Tom Atkinson <nibblercoppermine-gallery.net> wrote:

> Hello,
>
> I am attempting to convert this code for generating the digits of pi
> from the original C (below) to PHP.

is this for codegolf?

Kevin

--
"Democracy is two wolves and a lamb voting on what to have for lunch.
Liberty is a well-armed lamb contesting the vote."

attached mail follows:

Yes, it is.

Kevin Waterson wrote:
> This one time, at band camp, Tom Atkinson <nibblercoppermine-gallery.net> wrote:
>
>> Hello,
>>
>> I am attempting to convert this code for generating the digits of pi
>> from the original C (below) to PHP.
>
> is this for codegolf?
>
> Kevin
>

attached mail follows:

On 9/21/06, Kevin Waterson <kevinoceania.net> wrote:
> This one time, at band camp, Tom Atkinson <nibblercoppermine-gallery.net> wrote:

heh.. nice little twist.

Curt.

attached mail follows:

On 9/21/06, Tom Atkinson <nibblercoppermine-gallery.net> wrote:
> Hello,
>
> I am attempting to convert this code for generating the digits of pi
> from the original C (below) to PHP.
>
> long k=4e3,p,a[337],q,t=1e3;
> main(j){for(;a[j=q=0]+=2,--k;)
> for(p=1+2*k;j<337;q=a[j]*k+q%p*t,a[j++]=q/p)
> k!=j>2?:printf("%.3d",a[j-2]%t+q/p/t);}

wow this is rather bad. it would probably be better to write this in
asm, it would be easier to read than the way it is in C.

>
> I converted this to a more readable form:

what about using:
  php.net/pi

note the precision description.

or are we talking about a different pi.

Curt.

attached mail follows:

This one time, at band camp, "Curt Zirzow" <czirzowgmail.com> wrote:

> what about using:
> php.net/pi
>
> note the precision description.
>
> or are we talking about a different pi.

The goal of the codegolf.com challenge is to print pi to 1000 places.
The programmer to do it in the least keystrokes is the winner.

Kevin

--
"Democracy is two wolves and a lamb voting on what to have for lunch.
Liberty is a well-armed lamb contesting the vote."

attached mail follows:

pi() does not give me enough decimal places, I need the first 1000.

Curt Zirzow wrote:
> On 9/21/06, Tom Atkinson <nibblercoppermine-gallery.net> wrote:
>> Hello,
>>
>> I am attempting to convert this code for generating the digits of pi
>> from the original C (below) to PHP.
>>
>> long k=4e3,p,a[337],q,t=1e3;
>> main(j){for(;a[j=q=0]+=2,--k;)
>> for(p=1+2*k;j<337;q=a[j]*k+q%p*t,a[j++]=q/p)
>> k!=j>2?:printf("%.3d",a[j-2]%t+q/p/t);}
>
>
> wow this is rather bad. it would probably be better to write this in
> asm, it would be easier to read than the way it is in C.
>
>>
>> I converted this to a more readable form:
>
> what about using:
> php.net/pi
>
> note the precision description.
>
> or are we talking about a different pi.
>
>
> Curt.

attached mail follows:

Definitely looks like a grouping and/or precedence problem. Wish I
had more time to examine it. Fine-tooth those parens again.

-Christopher

attached mail follows:

I have solved the problem. The variables are declared as and forced to
remain integers in C but PHP converts them to float during division.
This messed up the maths. Also there was a slight difference in
formatting for printf().

Tom Atkinson wrote:
> Hello,
>
> I am attempting to convert this code for generating the digits of pi
> from the original C (below) to PHP.
>
> long k=4e3,p,a[337],q,t=1e3;
> main(j){for(;a[j=q=0]+=2,--k;)
> for(p=1+2*k;j<337;q=a[j]*k+q%p*t,a[j++]=q/p)
> k!=j>2?:printf("%.3d",a[j-2]%t+q/p/t);}
>
> I converted this to a more readable form:
>
> long k=4e3;
> int p;
> int a[337];
> int q;
> int t=1e3;
>
> main(j){
> for(;a[j=q=0]+=2,--k;){
> for(p=1+(2*k);j<337;q=(a[j]*k)+((q%p)*t),a[j++]=(q/p)){
> if (j>2 && k==1) printf("%.3d",(a[j-2]%t)+((q/p)/t));
> }
> }
> }
>
> and then changed it to PHP syntax
>
> $k=4e3;
> $p=0;
> $a=array();
> $q=0;
> $t=1e3;
>
> for(;$a[$j=$q=0]+=2,--$k;){
> for($p=1+(2*$k);$j<337;$q=($a[$j]*$k)+(($q%$p)*$t),$a[$j++]=($q/$p)){
> if ($j>2 && $k==1) printf("%.3d",($a[$j-2]%$t)+(($q/$p)/$t));
> }
> }
>
> The C code correctly gives me pi, but the PHP code gives me some other
> number which is not pi.
>
> What am I missing?
>
> Tom.

attached mail follows:

-----Original Message-----
From: Michelle Konzack [mailto:linux4michellefreenet.de]
Sent: 19 September 2006 11:14
To: php-generallists.php.net
Subject: [PHP] Re: Frustrated trying to get help from your site

Am 2006-09-18 14:43:12, schrieb Jon Anderson:

> As an aside, I think that the online and offline (downloadable) PHP
> documentation is probably the clearest, best organized and complete set
> of documentation for any programming language I've run into online.

I wish, the downloadable documentation would include all those
examples since this is, WHY the Documentation is realy great.

--

I'm not sure which examples you're referring to but if you mean the user
contributed notes then the download documentation does include this - at
least one of the .chm versions does. It's great, but you need to download it
regularly if you want the latest notes (obviously). Use one of the skins and
it's even better (I use the phpZ skin which displays a tab for the user
notes).

Cheers
Arno

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]