[Flow] CGL Filenames
Marc Neuhaus
apocalip at gmail.com
Thu Nov 20 10:16:09 CET 2014
Hey,
afaik, those example would currently break the ClassLoading, or did you
mean:
class Foo{} ==> Foo.php
abstract class AbstractFoo{} ==> AbstractFoo.php
interface FooInterface {} ==> FooInterface.php
trait FooTrait{} ==> FooTrait.php
Thats the way we do most of them already, but we could make it proper cgl
requirement i quess :)
Cheers
Marc
2014-11-20 10:07 GMT+01:00 Carsten Bleicker <carsten at bleicker.de>:
> class foo{} ==> Foo.php
> abstract class foo{} ==> AbstractFoo.php
> interface foo {} ==> InterfaceFoo.php
> trait foo{} ==> TraitFoo.php
>
> i would prefer the cgl that these has to end up filenames reflecting the
> type and name.
> currently there is no rule to build up classname with abstract/trait
> information like we did for interfaces.
> but i think its usefull to get those infos from the filename directly.
> currently interface is FooInterface. i would also prefer to change this cgl
> to InterfaceFoo to name them exactly like you code them "$TYPE $Name{}"
>
>
> ----------------------
>
> Carsten Bleicker
> Wülfingstraße 1
> 42477 Radevormwald
>
> E-Mail: carsten at bleicker.de
> Web: www.bleicker.de
> Twitter: @carstenbleicker
> Jabber: cbleicker at jabber.ccc.de
> Telefon: +49 (0)171-2690845
>
>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>
More information about the Flow
mailing list