Re: echo, log info and gen_* files

(For list history purposes) Wez' advice is that there isn't another approach that I could take, so the debugging info should be written to php://stderr instead - which is where it's sent by default anyway. We need a) to remove the 'echo' call and b) to set it so that all the config logging info per run is appended to the same file, if possible. Cheers, - Steph (going on to fight with nmake now that's sorted) ----- Original Message ----- From: "Steph" <steph@zend.com> To: "Christian Weiske" <cweiske@cweiske.de> Cc: "PHP-GTK dev" <php-gtk-dev@lists.php.net> Sent: Sunday, August 07, 2005 11:41 AM Subject: Re: [PHP-GTK-DEV] echo, log info and gen_* files > > >>No. That's just a message for the php-gtk developers which do the > > >>reflection infos (that is, me). > > > Do you need it to go to stdout for reflection to work? or just for > > > debugging? > > Debugging. The functions listed there have reflection infos, but they > > aren't used. It would be a shame to waste them. > > > > >>>Does anyone really need it to be echoed when it has the potential to be > > >>>fully logged? Or do I need to find a way that doesn't pick up stdout? > > >>I can disable it if you want to. > > > Thanks, but hold back a bit - it's probably best to wait for Wez to wake > up > > > and respond, he'll know if there's a way around it. > > > > It's really only for debugging. If everything is ok with the implemented > > arginfos, there wouldn't be any message. So it is an indicator that > > there is something which should be fixed. > > I was getting the full summary - headings and pretty formatting and all :) - > because log_print() is called every time configure does something right, as > well as when it does something wrong... > > Do you get to see your debug info if you set "generator.php -l php://stdout" > (etc etc etc)? > > -- > PHP-GTK Development Mailing List (http://gtk.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >