Never mind. Functions aren't autoloaded so it can't be moved to  
another file.

Kris

On May 17, 2009, at 20:46, Thomas Rabaix <[email protected]>  
wrote:

> the problem can be solve by adding an extra ' ' (space) after the '?>'
>
> On Sun, May 17, 2009 at 7:19 PM, Kris Wallsmith 
> <[email protected] 
> > wrote:
> If it's legacy symfony, can we move it out of the YAML component,  
> maybe into sfToolkit?
>
> --
>
> Kris Wallsmith | Community Manager
> [email protected]
> Portland, Oregon USA
>
> http://twitter.com/kriswallsmith
>
> On May 16, 2009, at 9:09 AM, Fabien Potencier wrote:
>
>>
>> No, it is an old shortcut function that can be useful when you  
>> embed PHP
>> inside a yaml string:
>>
>> foo: <?php echo 'foo' ?>
>> bar: baz
>>
>> The previous snippet won't work because you need to add a \n at the  
>> end:
>>
>> foo: <?php echo 'foo'."\n" ?>
>> bar: baz
>>
>> or
>>
>> foo: <?php echoln('foo') ?>
>> bar: baz
>>
>> So, for BC, we cannot remove it, even if I don't document it anymore.
>>
>> Fabien
>>
>> --
>> Fabien Potencier
>> Sensio CEO - symfony lead developer
>> sensiolabs.com | symfony-project.org | fabien.potencier.org
>> Tél: +33 1 40 99 80 80
>>
>>
>> Kris Wallsmith wrote:
>>> There is a function defined at the bottom of the sfYaml file,  
>>> echoln,
>>> that does not appear to be used anywhere in the YAML component.  
>>> Can this
>>> function be removed?
>>>
>>> Kris
>>>
>>> --
>>>
>>> *Kris Wallsmith* | Community Manager
>>> [email protected]
>>> <mailto:[email protected]>
>>> Portland, Oregon USA
>>>
>>> http://twitter.com/kriswallsmith
>>>
>>
>>>
>>>>
>>
>>
>>
>>
>
>
>
>
>
>
> -- 
> Thomas Rabaix
> http://rabaix.net
>
> >

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to