I finally got around to this test case with our SPOT browser and have
to RJ / the decision makers on this issue.
While it is true like Petr says that CCXML forbids you to make
vars that have not been declared - that section needs to be modified or
Like it or not, the contents of the <script> tag take you into
ECMA land. It is perfectly
legal to make assignments in ECMA to vars that weren't previously
declared as a var.
I'm not sure why CCXML thinks it has the authority to constrain what
When I originally read the section Petr reference some time back, it
struck me as a style
issue rather than something that can be enforced. It can be enforced to
some degree in CCXML's
<assign> tag by just doing a var; prior to assignment, but good
luck enforcing that inside <script>
Perhaps the section means that CCXML should enforce the rule when it
can outside of the <script>
tag. What happens in Vegas stays in Vegas and what happens in
<script> stays in <script>...
RJ Auburn wrote:
This is tracked as ISSUE-683.
CTO, Voxeo Corporation
Come join us at our Voxeo Customer Summit, June 21st – June 23rd at the Hard Rock Hotel, register today for your All Access Pass:
On Apr 13, 2010, at 8:51 PM, Petr Kuba wrote:
1) Assignment without declaration.
Script 8_2_2_A.txml, Assertions 757, 758, 759.
The script contains the following assignments without declaring variables var2 and var3:
var2 = var1;
var3 = myAry["ary"];
CCXML specification contains the following statement:
It is illegal to make an assignment to a variable that has not been
explicitly declared using <var> or a var statement within a <script>.
So the code above is illegal.
Interact Incorporated R&D