<p>Thanks Benjamin. It is my first proposal and I am not very "fluent" with the proccess. I want to "clean" the code and adjust it to the "coding standards" before move it for review. I am needing some help with the PHP Unit Testing because I never used it before. If someone can helps me on that would be good.</p>

<p>Anyway I will do an effort to place it for review asap.</p>

<p>Thanks again for your comments.</p>

<ac:macro ac:name="note"><ac:parameter ac:name="title">Zend Acceptance</ac:parameter><ac:rich-text-body>
<p>This proposal has been accepted for immediate development in the standard incubator.</p></ac:rich-text-body></ac:macro>

<p>Here is my offer as what shift cart with place.</p>

<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
<?php

require_once 'Zend/Json.php';

class Zend_Json_Expr
{
protected $_expression;

public function __construct($expression)

/**

• Don't need to to re-code the Zend_Json encoding proccess!!!
• Currently Zend_Json does not support this feature and
• this will be not create some problems for earlier created components
  *
• This feature is specific use only and may used by some needs.
• Zend_Json does not need to require Zend_Json_Expr.
• Zend_Json_Expr used by itself Zend_Json.
  */
  public static function encode($valueToEncode, $cycleCheck = false, $options = array())
  {
  $javascriptExpressions = array();
  //pre-proccessing
  $valueToEncode = self::_preprocessValue($valueToEncode, $javascriptExpressions);

$encodedResult = Zend_Json::encode($valueToEncode, $cycleCheck, $options);

//post-proccessing
if(count($javascriptExpressions) > 0) {
for($i = 0; $i < count($javascriptExpressions); $i++)

}

return $encodedResult;
}

/**

• Support UTF keys and values in arrays
• Support UTF values in objects
  */
  protected static function _preprocessValue(&$value, array &$javascriptExpressions, &$currentKey = null, $touchKey = false)
  {
  if($value instanceof Zend_Json_Expr) {
  $count = count($javascriptExpressions);

if($touchKey)

else

$magicValue = "___Zend_Json_Expression_Value".($count);
$javascriptExpressions[] = array(
"key" => $currentKey,
"value" => $value->__toString(),
"magicKey" => $magicKey,
"magicValue" => $magicValue
);
// value may contains UTF chars
// we always replacing value by a trusted (magic) value
$value = $magicValue;
// if key an index of array it may contains UTF chars
// we don't trust it
// we are replacing original key by your magic (Non-UTF) key if needs
if($touchKey)

// else leave $currentKey as it is
} elseif(is_array($value)) {
// here we save original keys order
$keys = array_keys($value);
$value2 = array();
foreach($keys AS $k1)

$value = $value2;
} elseif(is_object($value)) {
foreach($value AS $k => $v)

}
return $value;
}

public function __toString()

}
]]></ac:plain-text-body></ac:macro>

<p>Hi Inozemtcev,</p>

<p>Thanks for your offer. I have checked the code and have interesting points. Anyway I need to analyze it deeper.</p>

<p>UTF8 supporting is important, and that is good from your code!.</p>

<p>About having the "encode" method inside Zend_Json_Expr and don´t recode Zend_Json. I am not sure about it. I think that OOP good practice should keep the encode method in Zend_Json object. </p>

<p>I have not clear when and from where are you going to invoque Zend_Json_Expr->encode method. I mean, if I want to encode lets say an array with javascript expressions to encode, you purpose to use Zend_Json_Expr::encode() instead of Zend_Json::encode(), don´t you?.</p>

<p>Can you include a User Case for your code?. </p>

<p>Thanks for your help!</p>

<p>Before viewing this proposal, I've written an Issue (<a class="external-link" href="http://framework.zend.com/issues/browse/ZF-5974">http://framework.zend.com/issues/browse/ZF-5974</a>) doing something similar.</p>

<p>My fix works only with the internal encoder but maybe it's a cleaner way to do it. I've already contacted the maintainer of ext/json to know what will be the future behavior (or at least what it should be) int the php extension.</p>

<p>Has this proposal been abandoned? Please reply here.</p>

<p>If it's waiting in incubator, why does the reference guide actually list this functionality and provides an overview of it? There is no note that this feature is not yet available in the redistribution.</p>

<p>I like the idea of the proposal, but I think that it is not legal to encode a function name into a JSON object.</p>

<p><a class="external-link" href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a></p>

<p>Specifically, look at section "2.1 Values".</p>

<p>This means that any compliant JSON parser will fail if you use a Zend_Json_Expr. </p>

<p>The only workaround is to eval() the expression – but then its not JSON anymore, its just arbitrary javascript.</p>