[TYPO3-core] USER_CINT again

Martin Kutschker Martin.Kutschker at blackbox.net
Tue Feb 28 16:03:40 CET 2006


Dmitry Dulepov <dima at spamcop.net> writes on 
Tue, 28 Feb 2006 08:17:06 +0100 (MET):

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi!
> 
> Martin Kutschker wrote:
> 
> >> It's me and the infamous USER_CINT. Attached is the patch and a
> > > demo
> >> plugin.
> > 
> > 
> > Any comments?
> 
> I like the idea but I do not like returning boolean at first time and
> string at second time. We work with objects, there should be separate
> methods for such functionality. Something like "stateFunc" definition
> in TS setup, which should be called to provide current state: cached
> or not cached. This is a cleaner way.


You mean, TYPO3 should call a method (via TS stateFunc) first that returns the mode. And then it shall call the object again (the TS userFunc)?

Hm, the problem is that userFunc takes a complete definition of the object. So for two calls we have to create two instances.

Or an I create a locally persistent object? I mean a thingy I can call again in my context, but which isn't available for all the code. AFAIK the persistent objects are stored in some global array.

Masi 



More information about the TYPO3-team-core mailing list