[PHP-DOC] cvs: phpdoc /en/language oop5.xml
curtSat Aug 14 20:17:30 2004 EDT Modified files: /phpdoc/en/language oop5.xml Log: link oop5.basic and oop5.exceptions http://cvs.php.net/diff.php/phpdoc/en/language/oop5.xml?r1=1.5&r2=1.6&ty=u Index: phpdoc/en/language/oop5.xml diff -u phpdoc/en/language/oop5.xml:1.5 phpdoc/en/language/oop5.xml:1.6 --- phpdoc/en/language/oop5.xml:1.5 Sun Jul 11 08:33:25 2004 +++ phpdoc/en/language/oop5.xml Sat Aug 14 20:17:30 2004 @@ -1,15 +1,17 @@ - + Classes and Objects (PHP 5) Introduction - - Intro to oop5 for php - + +In PHP 5 there is a new Object Model. PHP's handling of objects has been +completely rewritten, allowing for better performance and more features. + + &language.oop5.basic; &language.oop5.decon; &language.oop5.visibility; &language.oop5.paamayim-nekudotayim; @@ -21,6 +23,7 @@ &language.oop5.iterations; &language.oop5.magic; &language.oop5.final; + &language.oop5.exceptions; &language.oop5.cloning; &language.oop5.object-comparison; &language.oop5.reflection;
[PHP-DOC] cvs: phpdoc /en/language/oop5 basic.xml
curtSat Aug 14 20:17:12 2004 EDT Added files: /phpdoc/en/language/oop5basic.xml Log: New basic oop5 documentation http://cvs.php.net/co.php/phpdoc/en/language/oop5/basic.xml?r=1.1&p=1 Index: phpdoc/en/language/oop5/basic.xml +++ phpdoc/en/language/oop5/basic.xml The Basics class Every class definition begins with the keyword class, followed by a class name, which can be any name that isn't a reserverd word in PHP. Followed by A pair of curly braces, of which contains the definition of the classes members and methods. Within each method, except for static methods, a psudo variable $this is available. $this is a reference to the same instance that called the method. Simple Class definition new To create an instance of an object, a new object must be created and assigned to a variable. An object will always be assigned when creating a new object unless the object has a constructor defined that throws an exception on error. Creating an instance When assigning an already created instance of an object to a new variable, the new variable will access the same instance as the object that was assigned. This behaviour is the same when passing instances to a function. A new instance of an already created object can be made by cloning it. Object Assignment &example.outputs; extend A class can inherit methods and members of another class by using the extend keyword in the declaration. It is not possible to extend multiple classes, a class can only inherit one base class. The inherited methods and members can be overloaded, unless the parent class has defined a method as final, by redeclaring them within the same name defined in the parent class. It is possible to access the overloaded method or members by referencing them with parent:: Simple Class Inherintance &example.outputs;
[PHP-DOC] cvs: phpdoc /en/language/oop5 exceptions.xml
curtSat Aug 14 20:14:46 2004 EDT Added files: /phpdoc/en/language/oop5exceptions.xml Log: New but empty exception page http://cvs.php.net/co.php/phpdoc/en/language/oop5/exceptions.xml?r=1.1&p=1 Index: phpdoc/en/language/oop5/exceptions.xml +++ phpdoc/en/language/oop5/exceptions.xml Exceptions .
Re: [PHP-DOC] Livedocs Status?
Wez Furlong wrote: Instead of non-specific "head is broken" email, why not point out what is broken? Please see http://news.php.net/php.doc/969363165. I wasn't just spouting "it's broke -- fix it". Perhaps these aren't problems for other people, but as I said in that post, I wasn't the only one fighting a livedocs install. We've already said that if a steady stream of good patches come in, more karma can be granted. I didn't understand that this was a possibility. Thanks for clearing that up. S
Re: [PHP-DOC] Livedocs Status?
Ilia, I reviewed the patches and applied 7 of them, thanks guys. The Cygwin patch was not applied because I have not way to test it and the last person I spoke to who build the manual on win32 via Cygwin had no issues. What in HEAD is broken? Thank you very much. I know you're busy, I really appreciate your attention. HEAD, see http://news.php.net/php.doc/969363165 Nuno did not have these problems, but Curt Zirzow helped me install, and he had some of the same problems (VACUUM, etc) -- perhaps my software was out of date. Follow, Nuno example :-). He is doing great work, which for the most part gets into CVS once Wez or I have the time to review it. It seemed that this process was not working, hence my email. I was wrong. Now that we've seen this process work, it seems productive to contribute. Thanks again. (-: There are some critical bugs in the code in particular dealing with pregeneration logic that fails to create some pages. While it's mostly self contained inside pregenerate.php there are some spillbacks to other files. Until that is resolved I'd like to keep once branch only, once that is fixed we can tag a "stable" release as that's the only major issue I am aware of at this point. That sounds great (the tags, not the bugs (-: ). I look forward to a livedocs-stable. Thanks again, Ilia. Nuno, thanks to you, too. S
[PHP-DOC] cvs: phpdoc /en/reference/xattr/functions xattr-list.xml
mg Sat Aug 14 19:46:10 2004 EDT Modified files: /phpdoc/en/reference/xattr/functionsxattr-list.xml Log: Add link to types manual. http://cvs.php.net/diff.php/phpdoc/en/reference/xattr/functions/xattr-list.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/xattr/functions/xattr-list.xml diff -u phpdoc/en/reference/xattr/functions/xattr-list.xml:1.1 phpdoc/en/reference/xattr/functions/xattr-list.xml:1.2 --- phpdoc/en/reference/xattr/functions/xattr-list.xml:1.1 Sat Aug 14 19:39:49 2004 +++ phpdoc/en/reference/xattr/functions/xattr-list.xml Sat Aug 14 19:46:10 2004 @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ - This function returns array with names of extended attributes. + This function returns array with names of extended attributes. See also xattr_get, xattr_set,
[PHP-DOC] cvs: phpdoc / manual.xml.in
mg Sat Aug 14 19:41:11 2004 EDT Modified files: /phpdoc manual.xml.in Log: Add xattr documentation. http://cvs.php.net/diff.php/phpdoc/manual.xml.in?r1=1.184&r2=1.185&ty=u Index: phpdoc/manual.xml.in diff -u phpdoc/manual.xml.in:1.184 phpdoc/manual.xml.in:1.185 --- phpdoc/manual.xml.in:1.184 Sun Aug 8 12:11:36 2004 +++ phpdoc/manual.xml.inSat Aug 14 19:41:11 2004 @@ -2,7 +2,7 @@ + @@ -238,6 +238,7 @@ &reference.vpopmail.reference; &reference.w32api.reference; &reference.wddx.reference; + &reference.xattr.reference; &reference.xml.reference; &reference.xmlrpc.reference; &reference.xdiff.reference;
[PHP-DOC] cvs: phpdoc /entities global.ent
mg Sat Aug 14 19:40:38 2004 EDT Modified files: /phpdoc/entitiesglobal.ent Log: Add xattr link. http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.193&r2=1.194&ty=u Index: phpdoc/entities/global.ent diff -u phpdoc/entities/global.ent:1.193 phpdoc/entities/global.ent:1.194 --- phpdoc/entities/global.ent:1.193Thu Aug 5 09:17:19 2004 +++ phpdoc/entities/global.ent Sat Aug 14 19:40:38 2004 @@ -1,6 +1,6 @@
[PHP-DOC] cvs: phpdoc /en/reference/xattr configure.xml constants.xml reference.xml /en/reference/xattr/functions xattr-get.xml xattr-list.xml xattr-remove.xml xattr-set.xml
mg Sat Aug 14 19:39:49 2004 EDT Added files: /phpdoc/en/reference/xattr configure.xml constants.xml reference.xml /phpdoc/en/reference/xattr/functionsxattr-get.xml xattr-list.xml xattr-remove.xml xattr-set.xml Log: Add xattr documentation. http://cvs.php.net/co.php/phpdoc/en/reference/xattr/configure.xml?r=1.1&p=1 Index: phpdoc/en/reference/xattr/configure.xml +++ phpdoc/en/reference/xattr/configure.xml &reftitle.install; xattr is currently available through PECL &url.pecl.package;xattr. If PEAR is available on your *nix-like system you can use the pear installer to install the xattr extension, by the following command: pear -v install xattr. You can always download the tar.gz package and install xattr by hand: xattr install by hand http://cvs.php.net/co.php/phpdoc/en/reference/xattr/constants.xml?r=1.1&p=1 Index: phpdoc/en/reference/xattr/constants.xml +++ phpdoc/en/reference/xattr/constants.xml &reftitle.constants; &extension.constants; XATTR_ROOT (integer) XATTR_DONTFOLLOW (integer) XATTR_CREATE (integer) XATTR_REPLACE (integer) http://cvs.php.net/co.php/phpdoc/en/reference/xattr/reference.xml?r=1.1&p=1 Index: phpdoc/en/reference/xattr/reference.xml +++ phpdoc/en/reference/xattr/reference.xml xattr Functions xattr &reftitle.intro; xattr extension allows to manipulate extended attributes on filesystems that support them. &reftitle.required; To use xattr, you will need libattr installed, available on the Linux XFS homepage &url.xattr;. &reference.xattr.configure; &reference.xattr.constants; &reference.xattr.functions; http://cvs.php.net/co.php/phpdoc/en/reference/xattr/functions/xattr-get.xml?r=1.1&p=1 Index: phpdoc/en/reference/xattr/functions/xattr-get.xml +++ phpdoc/en/reference/xattr/functions/xattr-get.xml xattr_get Get an extended attribute. Description stringxattr_get stringpath stringname intflags This function gets a value of an extended attribute named name of a file path. Extended attributes have two different namespaces: user and root namespace. User namespace is available for all users while root namespace is available only for user with root privileges. xattr operates on user namespace by default, but you can change that using flags argument. Supported xattr flags XATTR_DONTFOLLOW Do not follow the symbolic link but operate on symbolic link itself. XATTR_ROOT Set attribute in root (trusted) namespace. Requires root privileges. Returns string with value or &false; if attribute doesn't exist. See also xattr_set, xattr_remove, xattr_list. http://cvs.php.net/co.php/phpdoc/en/reference/xattr/functions/xattr-list.xml?r=1.1&p=1 Index: phpdoc/en/reference/xattr/functions/xattr-list.xml +++ phpdoc/en/reference/xattr/functions/xattr-list.xml xattr_list Get a list of extended attributes. Description arrayxattr_list stringpath intflags This functions gets a list of names of extended attributes of a file path. Extended attributes have two different namespaces: user and root namespace. User namespace is available for all users while root namespace is available only for user with root privileges. xattr operates on user namespace by default, but you can change that using flags argument. Supported xattr flags XATTR_DONTFOLLOW Do not follow the symbolic link but operate on symbolic link itself. XATTR_ROOT Set attribute in root (trusted) namespace. Requires root privileges. This function returns array with names of extended attributes. See also xattr_get, xattr_set, xattr_remove. http://cvs.php.net/co.php/phpdoc/en/reference/xattr/functions/xattr-remove.xml?r=1.1&p=1 Index: phpdoc/en/reference/xattr/functions/xattr-remove.xml +++ phpdoc/en/reference/xattr/functions/xattr-remove.xml xattr_remove Remove an extended attribute. Description boolxattr_remove stringpath stringname intflags This function removes an extended attribute named name of a file path.
Re: [PHP-DOC] Livedocs Status?
Instead of non-specific "head is broken" email, why not point out what is broken? Livedocs is running fine here; I built it only a week or so ago with no problems. Plus, I have a mirror that updates daily (livedocs.thebrainroom.net) with no problems (assuming that someone hasn't broken phpdoc) If you have a patch that works properly, by all means send it our way (either myself, Ilia, Derick or Goba). What we don't want is a half-baked patch that "fixes" stuff for one person/case and that breaks everything else; and that is the reason we tightened up the karma--some of us are *already* running livedocs in production. I've seen plenty of people say that livedocs isn't ready, but non of them have said why or come up with a firm list of what needs to be done to make it ready, let alone come up with patches for that. We've already said that if a steady stream of good patches come in, more karma can be granted. It's OpenSource: hack, send in patches. --Wez. PS: no need to pgp sign messages to a mailing list... On Sat, 14 Aug 2004 10:59:51 -0400, Sean Coates <[EMAIL PROTECTED]> wrote: > [This is a follow-up post to my previous post, "Livedocs woes".] > > What is the current status of livedocs development? > > My understanding is that anyone with phpdoc karma, also, once, had > livedocs karma. A commit was made that some maintainers did not like, > and karma was removed, and only granted to certain people (Currently: > iliaa,goba,wez,derick,sfox,alan_k). Please correct me if I am wrong. > > There are several outstanding issues with the livedocs code. As I said > in my post, last night, HEAD seems broken. Also, Nuno has a number of > patches available at http://livedocs.aborla.net/ > > My point? I'd like to determine the proper procedure for patching > (getting patches approved for) livedocs, or find an alternative > development method. > > I realize that livedocs is not ready for production, as it is intended. > It is, however VERY useful for doc team members (see Philip's posts re: > CHANGELOG and the EXIF changes he made for a practical example). > > I also understand that the original authors of livedocs don't want their > code messed with. Isn't this the beauty of CVS, though? > > I suspect this idea won't be well-received, but if we're not > willing/able to keep livedocs HEAD up to date, could we not branch the > module for testing purposes? Karma could be re-granted on a per-case > basis, with the condition that non-core developers do not commit to > HEAD, but to the dev branch. My understanding of the "staleness" of > livedocs is that Ilia and Wez are busy on PHP 5. I understand this. > People like Nuno, though, have demonstrated a knowledge of livedocs > code, and should be able to contribute, IMHO. I'd also like to see > livedocs tagged regularly so we can easily "rollback" to a previous > version (last night, while getting livedocs running, and failing > miserably, I was tempted to start pulling random dates out for cvs up -D ). > > I'm not trying to point fingers, here, I'd just like to see livedocs > move forward. Can we find a way to make this happen? > > > > S
[PHP-DOC] FW: [DOC-WEB] FW: [PHP-GTK] what is going on with gtk.php.net?
erm, that'll be docweb I'm thinking of. but the same applies ;) -Original Message--- From: Steph [mailto:[EMAIL PROTECTED] Sent: 15 August 2004 00:11 To: Gabor Hojtsy Cc: DOC-WEB; Andrei; PHPdoc Subject: RE: [DOC-WEB] FW: [PHP-GTK] what is going on with gtk.php.net? Goba, the bigger issue here is that the things you can do for a workaround (aka the mysqli coverage) isn't all that useful from our own perspective.. What we need to do is find something that is, and is also relevant to phpdoc and acceptable to the phpdoc and peardoc teams, before it gets to the point that more than two phpdoc'd OO items are covered in this way. PHPdoc promises to be a good forum to work this stuff through.. - Steph > -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 14 August 2004 23:22 > To: [EMAIL PROTECTED] > Cc: DOC-WEB; Andrei; PHPdoc > Subject: Re: [DOC-WEB] FW: [PHP-GTK] what is going on with gtk.php.net? > > > > I have to confess that this is the first time I've tried to look up > > 'connect' in the manual - and you're right, it doesn't work. The search > > there runs on a simple PHP script and I guess I misjudged the > percentage of > > 'like' that you'd need to get to retrieve that info from the > db. I remember > > writing it and being concerned chiefly not to return too much > if people put > > in something like 'set' or 'get' - 200+ returns on those queries wasn't > > helpful either. So maybe it's time to do as php.net do and > look into using > > htdig. And maybe, just maybe, I don't have the time to do that. > > Well, htdig is not used anymore because of performance reasons (it was > an exec()-ed CGI program). Now google is reused for queries and we have > a gold solution on the horizon. You guess it is named livedocs. It > includes preindexed superfast full text search. :) > > > I've said repeatedly that I will make sure that php-gtk-doc > > conforms with any OO documentation standard that the PHP > Documentation Team > > adopt. I still intend to do that. We can't have livedocs > development on > > the PHP-GTK project until that standard is decided. That > doesn't mean there > > haven't been attempts to adapt it, it just means we aren't > working in the > > same way at present - and nobody wants to see one set of rules > for PHP/PECL, > > another for PEAR and a third for PHP-GTK. So we need clear thinkers who > > understand the concepts and are prepared to assist in creating > a standard > > for the whole of php.net's OO coverage, as much as we need > people who are > > able to dig into C code and figure out what a function should > do (which is > > not always the same thing as it does do, that's what bug reports are all > > about). > > To sum this up, as far as I see, we need the concepts behind phpdoc > written down (in the documentation howto), so what structures we use, > and why do we do so are clear. Then this can be compared with PEAR and > PHP-GTK much easier. Now not much is written down about what tag level > structures we employ, but work is underway to define the big structures > (Philip is doing a good amount of work on this), and we are going into > the small details on the way. > > Goba
[PHP-DOC] RE: [DOC-WEB] FW: [PHP-GTK] what is going on with gtk.php.net?
Goba, the bigger issue here is that the things you can do for a workaround (aka the mysqli coverage) isn't all that useful from our own perspective.. What we need to do is find something that is, and is also relevant to phpdoc and acceptable to the phpdoc and peardoc teams, before it gets to the point that more than two phpdoc'd OO items are covered in this way. PHPdoc promises to be a good forum to work this stuff through.. - Steph > -Original Message- > From: Gabor Hojtsy [mailto:[EMAIL PROTECTED] > Sent: 14 August 2004 23:22 > To: [EMAIL PROTECTED] > Cc: DOC-WEB; Andrei; PHPdoc > Subject: Re: [DOC-WEB] FW: [PHP-GTK] what is going on with gtk.php.net? > > > > I have to confess that this is the first time I've tried to look up > > 'connect' in the manual - and you're right, it doesn't work. The search > > there runs on a simple PHP script and I guess I misjudged the > percentage of > > 'like' that you'd need to get to retrieve that info from the > db. I remember > > writing it and being concerned chiefly not to return too much > if people put > > in something like 'set' or 'get' - 200+ returns on those queries wasn't > > helpful either. So maybe it's time to do as php.net do and > look into using > > htdig. And maybe, just maybe, I don't have the time to do that. > > Well, htdig is not used anymore because of performance reasons (it was > an exec()-ed CGI program). Now google is reused for queries and we have > a gold solution on the horizon. You guess it is named livedocs. It > includes preindexed superfast full text search. :) > > > I've said repeatedly that I will make sure that php-gtk-doc > > conforms with any OO documentation standard that the PHP > Documentation Team > > adopt. I still intend to do that. We can't have livedocs > development on > > the PHP-GTK project until that standard is decided. That > doesn't mean there > > haven't been attempts to adapt it, it just means we aren't > working in the > > same way at present - and nobody wants to see one set of rules > for PHP/PECL, > > another for PEAR and a third for PHP-GTK. So we need clear thinkers who > > understand the concepts and are prepared to assist in creating > a standard > > for the whole of php.net's OO coverage, as much as we need > people who are > > able to dig into C code and figure out what a function should > do (which is > > not always the same thing as it does do, that's what bug reports are all > > about). > > To sum this up, as far as I see, we need the concepts behind phpdoc > written down (in the documentation howto), so what structures we use, > and why do we do so are clear. Then this can be compared with PEAR and > PHP-GTK much easier. Now not much is written down about what tag level > structures we employ, but work is underway to define the big structures > (Philip is doing a good amount of work on this), and we are going into > the small details on the way. > > Goba
[PHP-DOC] #24859 [Fbk->NoF]: OK Button Unavailable When You Add Application Mappings
ID: 24859 Updated by: [EMAIL PROTECTED] Reported By: cdoucette at med-learn dot com -Status: Feedback +Status: No Feedback Bug Type: Documentation problem Operating System: Windows XP Pro PHP Version: Irrelevant New Comment: No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: [2004-08-07 18:22:18] [EMAIL PROTECTED] Provided link doesn't work and KB318393 doesn't exist in MSDN. [2003-07-29 16:26:54] cdoucette at med-learn dot com Description: For anyone attempting to install PHP manually on Windows XP Pro with IIS 5.1, such as those of us trying to test the new PHP 5.0 beta 1, please note the following problem described in this Microsoft Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;318393 It would be great if you could add this to install.txt or the installation section of the online documentation (so we'd all know how to work around this IIS bug). This problem was also reported as bug #14041. Thanks, Chuck -- Edit this bug report at http://bugs.php.net/?id=24859&edit=1
[PHP-DOC] Re: [DOC-WEB] FW: [PHP-GTK] what is going on with gtk.php.net?
I have to confess that this is the first time I've tried to look up 'connect' in the manual - and you're right, it doesn't work. The search there runs on a simple PHP script and I guess I misjudged the percentage of 'like' that you'd need to get to retrieve that info from the db. I remember writing it and being concerned chiefly not to return too much if people put in something like 'set' or 'get' - 200+ returns on those queries wasn't helpful either. So maybe it's time to do as php.net do and look into using htdig. And maybe, just maybe, I don't have the time to do that. Well, htdig is not used anymore because of performance reasons (it was an exec()-ed CGI program). Now google is reused for queries and we have a gold solution on the horizon. You guess it is named livedocs. It includes preindexed superfast full text search. :) I've said repeatedly that I will make sure that php-gtk-doc conforms with any OO documentation standard that the PHP Documentation Team adopt. I still intend to do that. We can't have livedocs development on the PHP-GTK project until that standard is decided. That doesn't mean there haven't been attempts to adapt it, it just means we aren't working in the same way at present - and nobody wants to see one set of rules for PHP/PECL, another for PEAR and a third for PHP-GTK. So we need clear thinkers who understand the concepts and are prepared to assist in creating a standard for the whole of php.net's OO coverage, as much as we need people who are able to dig into C code and figure out what a function should do (which is not always the same thing as it does do, that's what bug reports are all about). To sum this up, as far as I see, we need the concepts behind phpdoc written down (in the documentation howto), so what structures we use, and why do we do so are clear. Then this can be compared with PEAR and PHP-GTK much easier. Now not much is written down about what tag level structures we employ, but work is underway to define the big structures (Philip is doing a good amount of work on this), and we are going into the small details on the way. Goba
Re: [PHP-DOC] Livedocs Status?
On August 14, 2004 04:23 pm, you wrote: > > There are several outstanding issues with the livedocs code. As I said > > in my post, last night, HEAD seems broken. Also, Nuno has a number of > > patches available at http://livedocs.aborla.net/ > > It would be nice if Ilia (and/or Wez) could review these patches, and > apply / comment on them. I reviewed the patches and applied 7 of them, thanks guys. The Cygwin patch was not applied because I have not way to test it and the last person I spoke to who build the manual on win32 via Cygwin had no issues. What in HEAD is broken? > > My point? I'd like to determine the proper procedure for patching > > (getting patches approved for) livedocs, or find an alternative > > development method. Follow, Nuno example :-). He is doing great work, which for the most part gets into CVS once Wez or I have the time to review it. > > I also understand that the original authors of livedocs don't want their > > code messed with. Isn't this the beauty of CVS, though Why commit if it'll be reverted. > > I suspect this idea won't be well-received, but if we're not > > willing/able to keep livedocs HEAD up to date, could we not branch the > > module for testing purposes? Karma could be re-granted on a per-case > > basis, with the condition that non-core developers do not commit to > > HEAD, but to the dev branch. My understanding of the "staleness" of > > livedocs is that Ilia and Wez are busy on PHP 5. I understand this. > > People like Nuno, though, have demonstrated a knowledge of livedocs > > code, and should be able to contribute, IMHO. I'd also like to see > > livedocs tagged regularly so we can easily "rollback" to a previous > > version (last night, while getting livedocs running, and failing > > miserably, I was tempted to start pulling random dates out for cvs up -D > > ). There are some critical bugs in the code in particular dealing with pregeneration logic that fails to create some pages. While it's mostly self contained inside pregenerate.php there are some spillbacks to other files. Until that is resolved I'd like to keep once branch only, once that is fixed we can tag a "stable" release as that's the only major issue I am aware of at this point. Ilia
[PHP-DOC] cvs: livedocs / handlers.php livedoc.php
iliaa Sat Aug 14 17:43:08 2004 EDT
Modified files:
/livedocs handlers.php livedoc.php
Log:
http://livedocs.aborla.net/patch.php?id=aliases.update&download=linux
http://cvs.php.net/diff.php/livedocs/handlers.php?r1=1.7&r2=1.8&ty=u
Index: livedocs/handlers.php
diff -u livedocs/handlers.php:1.7 livedocs/handlers.php:1.8
--- livedocs/handlers.php:1.7 Mon May 24 16:09:17 2004
+++ livedocs/handlers.php Sat Aug 14 17:43:08 2004
@@ -18,7 +18,7 @@
// | Special Handlers for $aliases|
// +--+
//
-// $Id: handlers.php,v 1.7 2004/05/24 20:09:17 iliaa Exp $
+// $Id: handlers.php,v 1.8 2004/08/14 21:43:08 iliaa Exp $
/***
@@ -27,9 +27,9 @@
function handle_appendixes_funcref()
{
- global $current_page_title, $children, $lang;
+ global $title, $children, $lang;
- $ret = "$current_page_title\n";
+ $ret = "$title\n";
foreach ($children as $id => $title) {
$url = generate_url_for_id($lang, $id);
$ret .= "$title\n";
http://cvs.php.net/diff.php/livedocs/livedoc.php?r1=1.107&r2=1.108&ty=u
Index: livedocs/livedoc.php
diff -u livedocs/livedoc.php:1.107 livedocs/livedoc.php:1.108
--- livedocs/livedoc.php:1.107 Tue May 25 07:33:48 2004
+++ livedocs/livedoc.phpSat Aug 14 17:43:08 2004
@@ -18,7 +18,7 @@
// | Generate an HTML version of a phpdoc/docbook page on the fly |
// +--+
//
-// $Id: livedoc.php,v 1.107 2004/05/25 11:33:48 wez Exp $
+// $Id: livedoc.php,v 1.108 2004/08/14 21:43:08 iliaa Exp $
define('LIVEDOC_SOURCE', dirname(__FILE__));
include LIVEDOC_SOURCE . '/livedoc_funcs.php';
@@ -61,20 +61,21 @@
'language.custom.functions' => 'handle_appendixes_funcref',
'language.basic.syntax' => 'handle_appendixes_funcref',
'language.variables' => 'handle_appendixes_funcref',
+ 'manual' => 'handle_contents'
);
} elseif (BUILD_TYPE == 'phpdoc') {
$aliases = array(
// For PHPdoc
'api' => 'streams',
'appendixes' => 'handle_appendixes_funcref',
- 'faq' => 'faq.general',
- 'features'=> 'features.http-auth',
+ 'faq' => 'handle_appendixes_funcref',
+ 'features'=> 'handle_appendixes_funcref',
'funcref' => 'handle_appendixes_funcref',
'getting-started' => 'introduction',
- 'installation'=> 'install.general',
- 'langref' => 'language.basic-syntax',
+ 'install' => 'handle_appendixes_funcref',
+ 'langref' => 'handle_appendixes_funcref',
'manual' => 'handle_contents',
- 'security'=> 'security.index',
+ 'security'=> 'handle_appendixes_funcref',
'indexes' => 'handle_index'
);
} else {
[PHP-DOC] cvs: livedocs / livedoc_funcs.php
iliaa Sat Aug 14 17:41:37 2004 EDT
Modified files:
/livedocs livedoc_funcs.php
Log:
Clean-up +
http://livedocs.aborla.net/patch.php?id=include.entities&download=linux
http://cvs.php.net/diff.php/livedocs/livedoc_funcs.php?r1=1.9&r2=1.10&ty=u
Index: livedocs/livedoc_funcs.php
diff -u livedocs/livedoc_funcs.php:1.9 livedocs/livedoc_funcs.php:1.10
--- livedocs/livedoc_funcs.php:1.9 Fri Jul 30 11:16:29 2004
+++ livedocs/livedoc_funcs.php Sat Aug 14 17:41:37 2004
@@ -214,7 +214,7 @@
$data = preg_replace('@@Usm', '', $data);
/* Replace entities */
- $data = bind_entities($data);
+ $data = str_replace($search, $replace, bind_entities($data));
/* catch any undefined entities */
if ($included) {
@@ -229,14 +229,11 @@
$data = preg_replace('@(<\\?xml.*\\?>)@U', '\\1', $data)
. '';
}
} else {
- $data = preg_replace('/&([a-zA-Z0-9-]+)\.([a-zA-Z0-9.-]+);/sm',
'', $data);
+ $data = preg_replace('/&([a-zA-Z0-9._-]+);/sm', '', $data);
}
- $data = str_replace($search, $replace, $data);
-
$page = new DocBookToHTML($data);
-
if ($return_rev) {
return array($page, $lang_rev);
} else {
@@ -250,10 +247,7 @@
if (empty($notes))
return '';
- $inner = <<
- User Contributed Notes
-HTML;
+ $inner = 'User Contributed
Notes';
foreach ($notes as $note) {
$date = date("d-M-Y h:i", $note['xwhen']);
@@ -262,16 +256,9 @@
$node->content = $note['note'];
$node->attributes['role'] = 'php';
$the_note = format_listing($node);
-
- $inner .= <<
-
- $note[who]
- $date
-
- $the_note
-
-HTML;
+
+ $inner .= ''.$note['who'].
+ ''.$date.''.$the_note.'';
}
return $inner . "";
@@ -384,12 +371,19 @@
return '';
}
+$GLOBALS['special'] = array('gt' => 1,'lt' => 1,'quot' => 1,'amp' => 1);
+
function handle_include($node)
{
global $current_page;
$ref = $node->attributes['ref'];
-
+
+ /* Special HTML entities */
+ if (isset($GLOBALS['special'][$ref])) {
+ return '&' . $ref . ';';
+ }
+
$curr_lvl = sqlite_single_query($GLOBALS['idx'], "SELECT lvl from toc where
docbook_id='$current_page'");
list($row) = sqlite_array_query($GLOBALS['idx'], "SELECT idents.id, lvl from
ents left join files on ents.value = files.filename left join idents on files.fileid =
idents.fileid left join toc on ents.entid=toc.docbook_id where is_file=1 and
ents.entid='$ref' limit 1");
@@ -404,7 +398,6 @@
}
if ($lvl > $curr_lvl) {
-
$fake->content = null;
$fake->attributes['linkend'] = $id;
$fake->tagname = 'xref';
[PHP-DOC] cvs: livedocs / build-ops.in build.sh configure.in mk_notes.php mkindex.php style_mapping.php toc.xsl /themes/default html_format.php
iliaa Sat Aug 14 17:34:05 2004 EDT
Modified files:
/livedocs build-ops.in build.sh configure.in mk_notes.php
mkindex.php style_mapping.php toc.xsl
/livedocs/themes/defaulthtml_format.php
Log:
Patches from http://livedocs.aborla.net/
build.misc
format_listing.nl
themes.default
toc-and-links
user-notes
http://cvs.php.net/diff.php/livedocs/build-ops.in?r1=1.8&r2=1.9&ty=u
Index: livedocs/build-ops.in
diff -u livedocs/build-ops.in:1.8 livedocs/build-ops.in:1.9
--- livedocs/build-ops.in:1.8 Tue May 4 21:35:41 2004
+++ livedocs/build-ops.in Sat Aug 14 17:34:05 2004
@@ -16,6 +16,5 @@
# "en" should be the first!
# LANGUAGES="en ar cs de es fi fr he hk hu it ja kr lt nl pl pt_BR ro ru sk sl sv tr
tw zh"
LANGUAGES="@LANGUAGES@"
-TOKEN="@TOKEN@"
-
[EMAIL PROTECTED]@
http://cvs.php.net/diff.php/livedocs/build.sh?r1=1.24&r2=1.25&ty=u
Index: livedocs/build.sh
diff -u livedocs/build.sh:1.24 livedocs/build.sh:1.25
--- livedocs/build.sh:1.24 Tue May 4 21:37:02 2004
+++ livedocs/build.sh Sat Aug 14 17:34:05 2004
@@ -6,10 +6,9 @@
echo ""
-if test -n "$TOKEN" ; then
- export TOKEN
+if test -n "$NOTES_MIRROR" ; then
echo "Building user notes"
- ${PHP} ${LIVEDOCSFORPHP}/mk_notes.php ${OUTPUTDIR}
+ ${PHP} ${LIVEDOCSFORPHP}/mk_notes.php ${OUTPUTDIR} ${GENDIR} ${NOTES_MIRROR}
fi
# running ./buildconf
@@ -63,4 +62,4 @@
echo -n "End: "
date
-#rm -f ${GENDIR}/toc-ugly.xml ${GENDIR}/toc-insert.sql
+rm -f ${GENDIR}/toc-ugly.xml ${GENDIR}/toc-insert.sql
http://cvs.php.net/diff.php/livedocs/configure.in?r1=1.27&r2=1.28&ty=u
Index: livedocs/configure.in
diff -u livedocs/configure.in:1.27 livedocs/configure.in:1.28
--- livedocs/configure.in:1.27 Fri Jul 30 11:19:25 2004
+++ livedocs/configure.in Sat Aug 14 17:34:05 2004
@@ -1,5 +1,5 @@
## A configure script
-## $Id: configure.in,v 1.27 2004/07/30 15:19:25 iliaa Exp $
+## $Id: configure.in,v 1.28 2004/08/14 21:34:05 iliaa Exp $
AC_PREREQ(2.13)
AC_INIT(livedoc.php)
@@ -83,9 +83,9 @@
fi
],[FORCE_DYNAMIC=1])
-AC_ARG_WITH(notes-token,[ --with-notes-token=token Token for fetching user
notes],
- [TOKEN="$withval"],
- [TOKEN=""])
+AC_ARG_WITH(notes-mirror,[ --with-notes-mirror=MIRROR Select a mirror to fetch
user notes (e.g. pt)],
+ [NOTES_MIRROR="$withval"],
+ [NOTES_MIRROR=""])
AC_ARG_WITH(web-base,[ --with-web-base[=DIR] Relative URL for livedocs
links [default=/]],
[WEBBASE="$withval"],
@@ -127,7 +127,7 @@
AC_SUBST(LIVEDOCSFORPHP)
AC_SUBST(OUTPUTDIRFORPHP)
AC_SUBST(XSLTPROC)
-AC_SUBST(TOKEN)
+AC_SUBST(NOTES_MIRROR)
AC_OUTPUT(build-ops config.php .htaccess)
@@ -135,8 +135,9 @@
AC_MSG_ERROR([HEY!! You should probably mkdir $OUTPUTDIR...])
else
echo "Copying livedoc files to $OUTPUTDIR..."
- cp common.php config.php .htaccess $OUTPUTDIR
+ cp config.php .htaccess $OUTPUTDIR
rm -f .htaccess
+ $lncmd $LIVEDOCS/common.php $OUTPUTDIR/common.php
$lncmd $LIVEDOCS/livedoc.php $OUTPUTDIR/index.php
$lncmd $LIVEDOCS/livedoc_funcs.php $OUTPUTDIR/livedoc_funcs.php
$lncmd $LIVEDOCS/error.php $OUTPUTDIR/error.php
http://cvs.php.net/diff.php/livedocs/mk_notes.php?r1=1.2&r2=1.3&ty=u
Index: livedocs/mk_notes.php
diff -u livedocs/mk_notes.php:1.2 livedocs/mk_notes.php:1.3
--- livedocs/mk_notes.php:1.2 Sun Aug 8 06:49:34 2004
+++ livedocs/mk_notes.php Sat Aug 14 17:34:05 2004
@@ -19,9 +19,7 @@
// | livedocs.|
// +--+
//
-// $Id: mk_notes.php,v 1.2 2004/08/08 10:49:34 goba Exp $
-
-$token = getenv("TOKEN");
+// $Id: mk_notes.php,v 1.3 2004/08/14 21:34:05 iliaa Exp $
$create = <
http://cvs.php.net/diff.php/live
[PHP-DOC] cvs: phpdoc /en/reference/bcompiler/functions bcompiler-write-class.xml
daveSat Aug 14 16:44:51 2004 EDT Modified files: /phpdoc/en/reference/bcompiler/functionsbcompiler-write-class.xml Log: - Typos. http://cvs.php.net/diff.php/phpdoc/en/reference/bcompiler/functions/bcompiler-write-class.xml?r1=1.2&r2=1.3&ty=u Index: phpdoc/en/reference/bcompiler/functions/bcompiler-write-class.xml diff -u phpdoc/en/reference/bcompiler/functions/bcompiler-write-class.xml:1.2 phpdoc/en/reference/bcompiler/functions/bcompiler-write-class.xml:1.3 --- phpdoc/en/reference/bcompiler/functions/bcompiler-write-class.xml:1.2 Fri Aug 13 12:12:04 2004 +++ phpdoc/en/reference/bcompiler/functions/bcompiler-write-class.xml Sat Aug 14 16:44:51 2004 @@ -1,5 +1,5 @@ - + @@ -17,9 +17,9 @@ &warn.experimental.func; This reads the bytecodes from PHP for an existing class, and writes them - to the open file handle, It does not perform dependancy checking, so make + to the open file handle, It does not perform dependency checking, so make sure you write the classes in an order that will not result in an - 'undefined class' occuring when you load it. + 'undefined class' occurring when you load it. bcompiler_write_class example
Re: [PHP-DOC] Livedocs woes
About my patches: I've posted that patches in my website just to don't lost them. Some are tested and can be commited, but some are just proof-of-concept. They can be used later by Ilia, Wez or Derick to fix the problems that I've found (and they may be aware of, but hadn't time to fix yet). The patches have a simple explanation of the problem and of my fix. Creating branches or even other module for livedocs isn't a solution IMHO. The best option is to have an oficial livedocs patch queue (this was proposed by the docs.php.net project), so that they can be reviewed, improved and commited/deleted. Since only you have pending patches currently against livedocs AFAIK, your queue is the only queue at this point in time. :) Goba
Re: [PHP-DOC] Livedocs Status?
What is the current status of livedocs development? Accepting patches (applied mostly by Ilia and Wez). There are several outstanding issues with the livedocs code. As I said in my post, last night, HEAD seems broken. Also, Nuno has a number of patches available at http://livedocs.aborla.net/ It would be nice if Ilia (and/or Wez) could review these patches, and apply / comment on them. My point? I'd like to determine the proper procedure for patching (getting patches approved for) livedocs, or find an alternative development method. I realize that livedocs is not ready for production, as it is intended. It is, however VERY useful for doc team members (see Philip's posts re: CHANGELOG and the EXIF changes he made for a practical example). I also understand that the original authors of livedocs don't want their code messed with. Isn't this the beauty of CVS, though? I suspect this idea won't be well-received, but if we're not willing/able to keep livedocs HEAD up to date, could we not branch the module for testing purposes? Karma could be re-granted on a per-case basis, with the condition that non-core developers do not commit to HEAD, but to the dev branch. My understanding of the "staleness" of livedocs is that Ilia and Wez are busy on PHP 5. I understand this. People like Nuno, though, have demonstrated a knowledge of livedocs code, and should be able to contribute, IMHO. I'd also like to see livedocs tagged regularly so we can easily "rollback" to a previous version (last night, while getting livedocs running, and failing miserably, I was tempted to start pulling random dates out for cvs up -D ). I'm not trying to point fingers, here, I'd just like to see livedocs move forward. Can we find a way to make this happen? All this is actually up to livedocs core developers (Ilia, Wez, Derick). BTW Derick offered a setup of livedocs to go for live testing at docs.php.net for this week. Goba
[PHP-DOC] cvs: phpdoc /en/reference/tidy/functions tidy-construct.xml
rioter Sat Aug 14 15:14:42 2004 EDT Modified files: /phpdoc/en/reference/tidy/functions tidy-construct.xml Log: fixed the spelling of initialze http://cvs.php.net/diff.php/phpdoc/en/reference/tidy/functions/tidy-construct.xml?r1=1.1&r2=1.2&ty=u Index: phpdoc/en/reference/tidy/functions/tidy-construct.xml diff -u phpdoc/en/reference/tidy/functions/tidy-construct.xml:1.1 phpdoc/en/reference/tidy/functions/tidy-construct.xml:1.2 --- phpdoc/en/reference/tidy/functions/tidy-construct.xml:1.1 Sun Jul 4 06:27:09 2004 +++ phpdoc/en/reference/tidy/functions/tidy-construct.xml Sat Aug 14 15:14:42 2004 @@ -1,5 +1,5 @@ - + tidy::__construct @@ -21,7 +21,7 @@ If the filename parameter is given, this function - will also read that file and initializate the object with the file, + will also read that file and initialize the object with the file, acting like tidy_parse_file. &tidy.conf-enc;
Re: [PHP-DOC] oop5 weaknesses
* Thus wrote Gabor Hojtsy: > Hi, > > The magic methods part and the intro still seems to be missing from the > oop5 section. It would be nice, if someone would be able to plug these > holes in. I'm working on that. There was a bug in php5's __sleep() that meeded some attention :) I've added a couple new sections as well: oop5.basics - Describes basic object creation and how objects are passed around via assignment and function parameters. oop5.exceptions - Exception handling. here is the current status of them so far: http://livedocs.zirzow.dyndns.org/index.php?l=en&q=language.oop5 Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid!
Re: [PHP-DOC] Livedocs woes
> For anyone with the same troubles, here's what I did: > 1) configure failed to detect my xsltproc binary, so I had to change > "XSLTPROC='no'" to "XSLTPROC=/usr/bin/xsltproc", otherwise, build.sh > fails because it doesn't know how to execute "no" maybe you don't have /usr/bin in the PATH :) the configure script does a AC_PATH_PROG to check automatically for the xsltproc path. > 2) when running build.sh, it bailed out complaining that the sqlite > database was full (in mkindex.php). This happened during VACUUM, which, > while beneficial, is not necessary, so comment out the line > "sqlite_query($idx, 'VACUUM full_search');" in mkindex.php This work perfectly on my two pcs. VACUUM is just a performance hack for SQLite. You need sqlite >= 2.8.1. > 3) when using any of the themes, I had to link /path/to/livedocs/themes > to /path/to/webroot/themes I never had problems with this... neither on windows or linux! > Other caveats: > - when giving configure a --with-build-log, build.sh is annoyingly > silent. It's much more convenient for me to ./build.sh | tee > my_own_build.log, and exclude that configure option. Livedocs build process is aimed to be run by cron... Just type the build command and relax :) Livedocs works! > - ignore the MANY lines that start with "BAD ID", when running build.sh, > I guess they don't matter. They exist, so they matter :) As livedocs is still in an earlier stage you will find many usefull debug info (some hidden in HTML comments). If you trace some problem, you can send me the info and I'll try to solve the problem. My programming skills aren't very good, but I'll try ;) About my patches: I've posted that patches in my website just to don't lost them. Some are tested and can be commited, but some are just proof-of-concept. They can be used later by Ilia, Wez or Derick to fix the problems that I've found (and they may be aware of, but hadn't time to fix yet). The patches have a simple explanation of the problem and of my fix. Creating branches or even other module for livedocs isn't a solution IMHO. The best option is to have an oficial livedocs patch queue (this was proposed by the docs.php.net project), so that they can be reviewed, improved and commited/deleted. Nuno
Re: [PHP-DOC] Livedocs Status?
Hi Sean, Currently the way of getting changes commited to the 'livedocs' in CVS is to submit patches to those who have karma. When submitting patches, remeber to do 'cvs diff -u' and save this patch to your website and mail them the link and explain to them what you are trying to do with the patch. Certain patches will not be commited and sometimes they will only after the commiter has changed the code slightly for coding standards or for some performance issues, etc. Regards --jm On Sat, 14 Aug 2004 10:59:51 -0400, Sean Coates <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > [This is a follow-up post to my previous post, "Livedocs woes".] > > What is the current status of livedocs development? > > My understanding is that anyone with phpdoc karma, also, once, had > livedocs karma. A commit was made that some maintainers did not like, > and karma was removed, and only granted to certain people (Currently: > iliaa,goba,wez,derick,sfox,alan_k). Please correct me if I am wrong. > > There are several outstanding issues with the livedocs code. As I said > in my post, last night, HEAD seems broken. Also, Nuno has a number of > patches available at http://livedocs.aborla.net/ > > My point? I'd like to determine the proper procedure for patching > (getting patches approved for) livedocs, or find an alternative > development method. > > I realize that livedocs is not ready for production, as it is intended. > It is, however VERY useful for doc team members (see Philip's posts re: > CHANGELOG and the EXIF changes he made for a practical example). > > I also understand that the original authors of livedocs don't want their > code messed with. Isn't this the beauty of CVS, though? > > I suspect this idea won't be well-received, but if we're not > willing/able to keep livedocs HEAD up to date, could we not branch the > module for testing purposes? Karma could be re-granted on a per-case > basis, with the condition that non-core developers do not commit to > HEAD, but to the dev branch. My understanding of the "staleness" of > livedocs is that Ilia and Wez are busy on PHP 5. I understand this. > People like Nuno, though, have demonstrated a knowledge of livedocs > code, and should be able to contribute, IMHO. I'd also like to see > livedocs tagged regularly so we can easily "rollback" to a previous > version (last night, while getting livedocs running, and failing > miserably, I was tempted to start pulling random dates out for cvs up -D ). > > I'm not trying to point fingers, here, I'd just like to see livedocs > move forward. Can we find a way to make this happen? > > > > S > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org > > iD8DBQFBHijnWppknrQMxQIRAtiKAKCCWFtGKzlPxyn4Y3pMydqMVvCT0gCfXQsJ > YihNZTBf+dl39Ch7BAODaNc= > =UqpZ > -END PGP SIGNATURE- > -- Jacques Marneweck http://www.powertrip.co.za/blog/
Re: [PHP-DOC] oop5 weaknesses
> The magic methods part and the intro still seems to be missing from the > oop5 section. It would be nice, if someone would be able to plug these > holes in. Just a FYI to eliminate any possible double work, Curt Zirzow is working on these (he got distracted by his php-src patching endeavors :). Regards, Philip
[PHP-DOC] Livedocs Status?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [This is a follow-up post to my previous post, "Livedocs woes".] What is the current status of livedocs development? My understanding is that anyone with phpdoc karma, also, once, had livedocs karma. A commit was made that some maintainers did not like, and karma was removed, and only granted to certain people (Currently: iliaa,goba,wez,derick,sfox,alan_k). Please correct me if I am wrong. There are several outstanding issues with the livedocs code. As I said in my post, last night, HEAD seems broken. Also, Nuno has a number of patches available at http://livedocs.aborla.net/ My point? I'd like to determine the proper procedure for patching (getting patches approved for) livedocs, or find an alternative development method. I realize that livedocs is not ready for production, as it is intended. It is, however VERY useful for doc team members (see Philip's posts re: CHANGELOG and the EXIF changes he made for a practical example). I also understand that the original authors of livedocs don't want their code messed with. Isn't this the beauty of CVS, though? I suspect this idea won't be well-received, but if we're not willing/able to keep livedocs HEAD up to date, could we not branch the module for testing purposes? Karma could be re-granted on a per-case basis, with the condition that non-core developers do not commit to HEAD, but to the dev branch. My understanding of the "staleness" of livedocs is that Ilia and Wez are busy on PHP 5. I understand this. People like Nuno, though, have demonstrated a knowledge of livedocs code, and should be able to contribute, IMHO. I'd also like to see livedocs tagged regularly so we can easily "rollback" to a previous version (last night, while getting livedocs running, and failing miserably, I was tempted to start pulling random dates out for cvs up -D ). I'm not trying to point fingers, here, I'd just like to see livedocs move forward. Can we find a way to make this happen? S -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBHijnWppknrQMxQIRAtiKAKCCWFtGKzlPxyn4Y3pMydqMVvCT0gCfXQsJ YihNZTBf+dl39Ch7BAODaNc= =UqpZ -END PGP SIGNATURE-
[PHP-DOC] #29677 [NEW]: imap_search and imap_open documentation is incomplete: missing charset option
From: jotta at mailbox dot hu Operating system: - PHP version: Irrelevant PHP Bug Type: Documentation problem Bug description: imap_search and imap_open documentation is incomplete: missing charset option Description: I was looking for a solution to specify a charset option for imap_search(). After a day long research, I've found, that this is supported in imap_search() and imap_open() for more than a year (patch was posted here: http://bugs.php.net/bug.php?id=22505 ), but it's still not documented. The documentation should read: array imap_sort ( resource stream, int criteria, int reverse [, int options [, string search_criteria [, string charset ]]]) and array imap_search ( resource imap_stream, string criteria, int options, string charset) The documentation might help users by telling which charsets are supported by the IMAP library: http://www.washington.edu/imap/IMAP-FAQs/index.html#1.12 It's tested and working under Linux and PHP 4.3.7 with an IMAP library version 2004 (that's imap-2004.tar.Z) -- Edit bug report at http://bugs.php.net/?id=29677&edit=1 -- Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=29677&r=trysnapshot4 Try a CVS snapshot (php5): http://bugs.php.net/fix.php?id=29677&r=trysnapshot5 Fixed in CVS: http://bugs.php.net/fix.php?id=29677&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=29677&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=29677&r=needtrace Need Reproduce Script: http://bugs.php.net/fix.php?id=29677&r=needscript Try newer version: http://bugs.php.net/fix.php?id=29677&r=oldversion Not developer issue:http://bugs.php.net/fix.php?id=29677&r=support Expected behavior: http://bugs.php.net/fix.php?id=29677&r=notwrong Not enough info:http://bugs.php.net/fix.php?id=29677&r=notenoughinfo Submitted twice:http://bugs.php.net/fix.php?id=29677&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=29677&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=29677&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=29677&r=dst IIS Stability: http://bugs.php.net/fix.php?id=29677&r=isapi Install GNU Sed:http://bugs.php.net/fix.php?id=29677&r=gnused Floating point limitations: http://bugs.php.net/fix.php?id=29677&r=float
[PHP-DOC] oop5 weaknesses
Hi, The magic methods part and the intro still seems to be missing from the oop5 section. It would be nice, if someone would be able to plug these holes in. Goba
