On Jan 10, 2005, at 1:41 PM, Justin M. Gregg wrote: [snip] I notice at this page: http://www.glossologia.org/wiki/index.php/Special:Listusers there is no user account "Bob" listed. -- brion vibber (brion @ pobox.com)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Edward Peschko wrote: | What do people use for a command-line IDE in debugging mediawiki, aside | from dbg (http:/dd.cron.ru/dbg) Mostly I just try to stick in a stack trace at fatal errors (as a general rule, using wfDebugDieBacktrace()) and occasionally slip in a temporary var_dump to see additional variable state. Crude, yes. | I've just about given up on the command line debugger there - and was wondering | whether php has any plans on integrating one into the php-suite, as perl does.. Zend (the developer of PHP) sells a proprietary, commercial IDE with an integrated debugger. Honestly I doubt they're interested in cutting into that market by integrating debugging tools into the open-source PHP core. They've so far kept bytecode caching out of the standard PHP distribution as well. - -- brion vibber (brion @ pobox.com)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Edward Peschko wrote: | On Sat, Jan 29, 2005 at 06:31:49PM -0800, Brion Vibber wrote: |>Mostly I just try to stick in a stack trace at fatal errors (as a |>general rule, using wfDebugDieBacktrace()) and occasionally slip in a |>temporary var_dump to see additional variable state. Crude, yes. |> | bleah. | | The wfDebugDieBacktrace() call would work well if you knew the codebase already, | what I was looking for was using the debugger as a teaching tool, to see | how the code was structured, and step through what it does. Well, that's a rather different question; you asked what we use for debugging. | And I *hate* graphical debugging environments. Do you know if Zend, dbg, or any | other IDE provides a cli interface? | | I've tried php-dev, but they are noticably silent on the whole issue... Basically, the world of debugging PHP is a really crappy world, which can barely support life. - -- brion vibber (brion @ pobox.com)

In good sadness, Ed: whence the accoutrement; why not `less', `grep', and a hard copy on cotton stock? -- Peter Danenberg . wikisophia.org ..:

hey all, a couple of questions - what are the prerequisites for running 'index.php' at the command line, eg: php index.php doesn't seem to do anything. Ultimately, I'd like to be able to run index.php sans browser and be able to debug based on the output that comes to standard out... Ed (ps - is there a good class pretty printer for php? I noticed that - unlike perl - var_export, print_r, etc, don't seem to handle classes very well. I'd like to be able to say: var_export($class_reference); and have php print out all the associated class variables and object variables. )

On Wed, Feb 23, 2005 at 11:22:59PM -0800, Brion Vibber wrote: so I get these environmental variables from what - the $_ENV and $_SERVER globals? Php seems to have sliced the environmental variables into these two associative arrays.. What if I need the variables in $_COOKIE and $_GET and $_POST? I'll give it a whirl, but I'm skeptical. I just tried it, got a '>' as a prompt, hit one question mark (to get help) and it seemed to spawn an infinite loop of '>' prompts. well, I mis-spoke. I wanted to print out an object, and it so happens that the object I chose (WebRequest) doesn't seem to have any object variables *or* class variables. Ed ( ps - ok, preemptive apology for the following rant, but this is seriously screwed up: "As of PHP 4.3.0, the name, location and existence of the CLI/CGI binaries will differ depending on how PHP is installed on your system. By default when executing make, both the CGI and CLI ere built and placed as sapi/cgi/php and sapi/cli/php, and NOTE THAT BOTH ARE NAMED PHP." It goes on to say that based on what compile options you use, ONE OR THE OTHER php is installed as php, and the other is ignored. I have a php CLI version, but I guess the wiki I installed works because I've got a: LoadModule php5_module libexec/libphp5.so statement inside of my httpd.conf, but this is just too whacked out. They've bifurcated the php code base whether or not your in a command line world or a CGI world?? Just curious, but why was php chosen in the first place? The more I look, the more php seems to be tied together with little bits of string and glue.. why not python or mod_perl, or ruby? Or, even c/C++, or *shudder* java? )

let me rephrase the question - is there a particular point inside of index.php that I could snapshot, which would have all the variables needed for a given index.php query, and could I take these variables, set the appropriate CGI environment up, and then run it seamlessly? Or is there going to be extra-environment information that I'm going to have to acquire (and massage) in order to make this work? I'm primarily thinking cookies here.. of course, but I would think that the appropriate response would be to emit a syntax error, not an infinite loop of '>'s . This just leads me to think that it might be not the most 'well-traveled' debugging environment. ... and made it rather difficult to have both flavors resident on your machine at the same time, In particular (for those who google on CLI and CGI problems with php), to get both cli and cgi, I needed to configure and compile php twice, once --with-apxs=, and once without. ;) ok, lets just say that we respectfully disagree here. AFAICT, php is one huge winnebago class, which survives by quick access to a bunch of quick-to-use functionality without needing to import various modules. (perl is a winnebago too, but about 5 times smaller, and perl has much more powerful data manipulation methods. Ed

Some cavaliers (Timwi, Magnus, Manfred) have made oeil- lades in that direction, Ed; and a C engine would enable us to dish out pages, say, as a native Apache handler. It's a big project, however; and the .php, being just functional enough, engenders a fatal inertia. -- Peter Danenberg . wikisophia.org ..: