Re: [PHP-DEV] GSoC - XDebug profiling web front-end
On Apr 1, 2009, at 3:33 AM, Derick Rethans wrote: I don't know what the state is tbh, but there is now also webgrind at http://code.google.com/p/webgrind/ Webgrind works, but could use some refinement. It doesn't do tree graphs yet, for one. It also doesn't support uploading files to it. -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Case sensitivity
On Nov 6, 2008, at 11:59 PM, Ronald Chmara wrote:
1. All built-in PHP functions should be aliased in the worlds most
used languages, so that declaring a function could also be written
as: funktsioon, otstarve, λειτουργία ,
ویرایش, Fonction, funcionar, fungsi, funzionare,
қызмет, 可算, メソッド, funkcja (etc.)
Can I get a +1?
+1, but it'd be a ++1 if we could also take into consideration
dyslexic programmers. I would like to be able to write:
} (oof$) cnuf_emos noitcnuf
;oof$ ohce
{
/me ducks
-T
P.S. No, I didn't do that programmatically. Lefties have tendencies
towards dyslexia which lets us write both ways without too much
thought :-)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] run-tests gsoc status?
Hey guys; On Aug 27, 2008, at 7:36 AM, Johannes Schlüter wrote: On Wed, 2008-08-27 at 10:46 +0200, Derick Rethans wrote: There was a run-tests.php rewrite application accepted for gsoc this summer.. I however haven't heard a word about it since then.. Does anyone know the status of that project? Still no reply to this? I suppose the project is then not going anywhere. Can any of the GSoC admins see if something happened with reviews here? Nothing happened there, neither student nor mentor filled out the final survey nor did I see any code. (but that's also true for projects doing quite well) Sorry about this guys. A large part of this is my fault. The time I could devote to this quickly evaporated as the summer wore on. I tried to get someone familiar with project to take over as mentor a little over half way through, but everyone else was tied up too. Couple that with someone that got in over their head and, well, the GSoC project just couldn't make it. All that said, I'm shooting for a 1.0 of PHPT by the end of the year. That will have complete running of the php-src tests, parallel test running, and full support for Windows (thanks in large part to all of the testing of PHPT that Elizabeth Smith has done). Michal - I would love to have some help on this. As I alluded to here, there is already a replacement for run-tests.php in the PHPT project (phpt.info). It's 0.1 release was a rewrite of PEAR_RunTest, so there are some discrepancies between what it can do currently and what run-tests is capable of. If you would like to help out, feel free to ping me off-list or on phpt-dev for some guidance. -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] run-tests gsoc status?
On Aug 27, 2008, at 10:30 AM, Sebastian Bergmann wrote: So the student worked on PHPT instead of run-tests.php? Yes, as we talked about earlier in the year on IRC and on the wiki. For those of you who don't know what PHPT is: It's a ground-up rewrite of the PEAR_RunTest code (which was based on run-tests.php) that addresses the short-comings in architecture that both PEAR_RunTest and run-tests.php have. It's about 90% of the way there to being able to completely run all of the .phpt files in php-src, it just needs some attention to clean up all of the loose ends. -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] CVS to SVN Migration
Hello Marcus; Marcus Boerger wrote: A cvs read-only mirror would be nice to allow the old way of checking out stuff. But there I fail to see the reason to limit our selves to one additional other tool, nor do I see a reason to complicate matters even more by giving people other repositories that we somehow merge or not. SVN works everywhere and other tools can be used on top of it where ppl see that necessary but it is not the way PHP is being developed. Or do you want to change the whole of PHP development at the same time? I don't presume to speak for Lukas here, nor to believe we should standardize on one particular alternative VCS (be it a DVCS or not). I think we should definitely go the SVN route as the only official way to commit to PHP with possibly a read-only mirror on CVS that could be phased out at some point in the future. That said, I think if someone is willing to step up to the plate and offer bootstrap repositories for another VCS and is willing to help support it for those who are interested in using it we would be remiss in turning them down as it's no small undertaking. According to the wiki there are over 270k commits in php-src. Using Mono (90k - 100k commits) and my own experience with smaller repositories (500 - 30k) as a guide, this means that to clone the entire history of PHP via a `git svn clone` command would take nearly a week! Using a bootstrap that is updated nightly, or even weekly, we can cut that process down to 15 minutes. I've already volunteered on the svn-migrations list to work on an unofficial mirror as soon as the SVN import is completed. I would love to see it make its way onto a php.net server so others who are interested can benefit from the upfront work, but will be happy to host it on one of my servers like the current git clone is. -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Volunteers for Subversion 1.5 conversion of cvs.php.net?
If it's not happening in the next month, I'd be happy to help. I did the SimpleTest CVS to SVN conversion in about 5 minutes (including waiting on the history to be converted). I've also worked with the hook scripts and such in SVN so I might be able to help out there if someone else doesn't already have it covered. On a slightly related note, would anyone else be interested in seeing a Git repository along side Subversion? Even if people can't commit to the Git repo, I'd be happy to help set it up with the ability for them to push changes back to the SVN repo once they've prepared their patches. -T Rasmus Lerdorf wrote: Now that Subversion 1.5 has been out for a little while and it is at the point where it might actually have some benefit to us, do we have some volunteers who have some time to try converting over the repository and all the post-commit and ACL rules from CVSROOT? Talking to people here at OSCON, the consensus seems to be that moving to Subversion at this point would worthwhile. The Git/Bzr/Merc folks have better tools to deal with a central svn repository than cvs at this point, and the svn workflow and Windows tools won't leave all our less technical committers floundering. I think the most convenient approach would be to do the conversion directly on the cvs.php.net machine and run the two side-by-side with periodic imports to svn while we test things and then a freeze and a switchover at some point. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] lstat call on each directory level
On Jul 15, 2008, at 2:25 PM, Rasmus Lerdorf wrote: Well, it is used in other places too, like in figuring out _once paths. Including the same file using different paths still needs to be caught. Are you calling clearstatcache() manually anywhere? That blows away the entire realpath cache and completely destroys your performance, so you will want to avoid doing that very often. Based on what I've seen, if the realpath cache gets filled it just quits caching rather than pruning. That seemed odd to me. There was also an issue that Dmitry had fixed in 5.3 a month or so ago where it was caching false finds and filling the cache up more quickly than necessary. I found this out through a quick extension I wrote to view the contents of the realpath cache. If anyone wants to clean this up for inclusion in the core, I'd be more than happy to have it there. You can grab a copy from my Git server: git://git.domain51.com/php.realpath.git -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [RFC] Namespaces for internal classes
Hey Lars; On Jul 3, 2008, at 4:07 AM, Lars Strojny wrote: one thing on my mind is the current naming of our internal classes. I could say the same for our functions but no, I don't have plans to save the universe, saving the world should be enough for now. So I've tried to dig through the ext/spl-package as an example how to implement namespaces for internal classes. Also I did it for SPL now, I would go on further and discuss such changes e.g. for ext/intl. And here is the resulting RFC: http://wiki.php.net/rfc/namespaces-for-internal-classes The RFC is not ready yet but I want to get feedback on it. The integral part is the list of renamings and that's fixed, so you can expect a bit more prose :) Having that for 5.3 seems like a good idea, as we have a) a number of added SPL classes, b) most likely new extensions introducing new classes (ext/intl, ext/phar), c) having it is 5.3 would allow us seemless transistions to newer PHP versions. +1 on the idea, but I'm not huge on the current naming structure. Here's just a few things that I would change: * Completely bike shedding, but does Recursive need its own level? RecursiveArray reads better than having Array at two different levels to me. * Again, bike shedding, but I like the name ArrayIterator - it defines exactly what the class is while Array doesn't convey very well by itself. You have to look at the full name in order to understand the process. This also becomes ambiguous when you're reading the code in PHP. What does $a = new Array($some_array); do? You have to go back to the uses declaration at the top to figure it out. This is true for most of the names I'm seeing here. Range, Info, Object, Logic, etc. What kind of Range, Info about what, a plain Object, an ArrayObject, or something else? You end up with more verbose names by going to a PEAR1 style of naming convention because you have to use the entire name with the namespace in order to convey what the code is supposed to be doing. I would stick with names more closely related to the original names and add spl:: (see next comment for lowerspace) to signify that they're part of SPL. So instead of RecursiveArrayIterator, you have spl::RecursiveArrayIterator; SplFileInfo becomes spl::FileInfo, etc. * I would change everything except the final class name in the full name to be lowercase. Using your existing examples: Spl::List::DoublyLinked would be spl::list::DoublyLinked, or better yet spl::DoublyLinkedList, etc. This helps denote what is a class and what is part of the namespace name. In the original examples, its ambiguous as to what can be instantiated. Are Spl and Spl::List classes that can be instantiated? Moving to the lower space convention makes it easy to denote what is a class and what is just part of the namespace. This follows the path created by several other languages. Thanks for bringing this up. Hopefully we can start using namespaces in at least some parts of PHP to help promote their best uses throughout the language. -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [PATCH] make it possible to skip very slow tests
On Jun 19, 2008, at 7:07 AM, Steph Fox wrote:
Yes, it is. Check the system_with_timeout() function in the run-
tests.php script.
There you've the timeout hardcoded ('$leak_check ? 300 : 60'). You
would just need to make it configurable by some environment var.
I already tried hard-coding both tv_sec and tv_usec to 0 and it
makes no difference here.
I can add this to PHPT - it uses a timeout based on reading the open
proc. The only problem is that it is currently treated as an error.
I could maybe add a new reporting level of timeout, though I do like
the idea of having some sort of meta-data to conditionally skip tests.
Maybe a better solution is to add an --exclude pattern and ask
people to either place potentially slow tests in tests/slow/, or name
then test case.slow.phpt? Being able to exclude a pattern of test
names definitely has more use than just setting a timeout.
Thoughts?
-T
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [PATCH] make it possible to skip very slow tests
On Jun 19, 2008, at 9:03 AM, Steph Fox wrote: There's nothing wrong with that approach. I'm trying to find something that addresses the problem (i.e., how can I not run tests that are going to take a long time to run?), while providing enough flexibility to answer other problems (i.e., how can I skip X tests that I don't care about?). If there's a way to address the problem without making it so specific, I'm all for it. I mostly agree - I'm just looking at 'here and now' rather than 'when the nice new test suite stuff is done'. 'Here and now', there isn't a reliable way to set this up and skipif looks like the cleanest option. The only problem with that is everything you add I've got to add to my GSoC project so PHPT :-) That might not be a bad idea. I think the long-term goal should be the ability to force skip files based on an --exclude parameter, an ini conf file (looks for -- ini-file file or cwd/tests.ini), and an ENV variable. The first and last would just be separated by the PATH_SEPARATOR for regex patterns. In addition, we can definitely make the time-out something that's settable via the command line and conf, but as you noted in your next email, that is a separate issue. I've created a few tickets on these so we can make sure to track these issues: * add exclude: http://phpt.info/ticket/69 * add timeout: http://phpt.info/ticket/70 -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [PATCH] make it possible to skip very slow tests
Hey Steph; On Jun 18, 2008, at 3:37 PM, Steph Fox wrote: I'm using this locally because two of our tests take over 10 minutes each to run on my laptop, and I run the relevant bits of test suite every time I make a change. All it does is adds another option, -x, to run-tests.php. This sets an environmental variable which can then be checked for in the SKIPIF section of very slow-running tests. How do you specify that test A is slow? Is there a certain skipif message you include, or...? -T -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] CVS Account Request: tswicegood
Various debauchery relating to php-src ;-) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
