Hmm, yes I realise it's more a complaint with SG. The only reason I posted it here was that I spotted a testimonial from a certain "David Zulke" on sourceguardian.com, and wondered if a) it was you, and b) you'd tried it in conjunction with Agavi.
David Zülke wrote: > That's something the SG folks have to look into ;) There are similar > errors when using eAccelerator, it's simply bugs in the encoders. > > > David > > > > Am 21.03.2007 um 13:07 schrieb Daniel Swarbrick: > >> Has anyone tried encoding their Agavi apps (not the Agavi shared >> source >> install) with Source Guardian? I'm getting some weird errors, that I >> think are starting to follow a pattern. >> >> I'm getting errors along the lines of: >> >> Fatal error: Declaration of ExportCSVSuccessView::execute() must be >> compatible with that of AgaviView::execute() >> >> when running the encoded version of ExportCSVSuccessView.class.php, >> but >> dropping in the unencoded version works fine. The majority of other >> classes in my app also seem to work fine, with one major exception >> - it >> seems that any class that has a method named execute() fails. >> >> I also had an instance of: >> >> Fatal error: Cannot access protected property FooModel::$dbConn >> >> which was also remedied by replacing the encoded version with the >> unencoded. There should be no difference in the actual derived PHP >> code. >> >> It's as if Source Guardian is clobbering some of my methods and >> variables!? >> >> I'm using Source Guardian 7.0, PHP 5.2.0, and the latest IXED loaders. >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.agavi.org/mailman/listinfo/users >> > > > _______________________________________________ > users mailing list > [email protected] > http://lists.agavi.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
