Hi Marijn, thank you very much, but unfortionately this does not solve my problem - though it *could* do so, with a little effort.
I explicitely want to extend sfValidatedFile because of two reasons: 1.) I want "my" file upload validator - which does a few things that the core sfValidatorFile cannot do - check against the "interface" sfValidatorFile by using the keyword instanceof. 2.) religion, i don't want to repeat myself. ;) So the intention is to rely on features that are already implemented without reinventing the wheel. Ok, i confess ... it is merly a question of principle. Of course i could do things as you've had suggested. But i am of the opinion that splitting the core file into 2 files, named sfValidatorFile.class.php and sfValidatedFile.class.php would simply avoid autoloading problems. In a later attempt i would even ask if the design of this class (namely sfValidatedFile) is a good idea at all - but for now it would be great if the .php file could be splitted into 2 (whithout touching a line of code) ;) Greetings .) On Jun 15, 1:17 pm, Marijn Huizendveld <[email protected]> wrote: > Hi, > > You could just use the sfValidatedFile > optionhttp://trac.symfony-project.org/browser/branches/1.2/lib/validator/sf... > > Than you could use your own validated file class. > > Kind regards, > > Marijn > > On Jun 13, 2009, at 12:30 PM, Johannes Heinen wrote: > > > > > Hi, > > > i discovered a really small issue that eventually needs a workaround > > by mastering a few config-files, but in my opinion could be easily > > solved by a little improvement. > > > The class sfValidatedFile is written in the same file that contains > > sfValidatorFile, which makes it inpossible to extend it by a third > > class if sfValidatorFile.class.php was not previously included (e.g. > > by instanciating sfValidatorFile, so that you take advantage from the > > spl autoload feature). > > > I would suggest to simply split the source file into 2 class files > > (sfValidatorFile.class.php and sfValidatedFile.class.php), that would > > provide a clean way to instanciate both classes independently and > > without explicit require statements. > > > What do you think about that? > > > With best regards, > > de joshi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
