[mashup-dev] jslint does not parse E4X - reports inline E4X code as fatal errors

[Keith Chapman]

Tyrell Perera wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Done and committed to svn trunk.
>
> Keith,
>
> Please include jslint to the build. The library is a single file
> downloadable from http://www.jslint.com/fulljslint.js
>   
Done.

Thanks,
Keith.
> Thanks,
>
> Tyrell
>
>
> Jonathan Marsh wrote:
>   
>> +1 to both having the option, and working to get jslint updated.  Perhaps we
>> could even devote some resource to the updates (after 1.0 is under our
>> belt...)
>>
>> Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
>>  
>>
>>     
>>> -----Original Message-----
>>> From: mashup-dev-bounces at wso2.org [mailto:mashup-dev-bounces at wso2.org]
>>> On Behalf Of Channa Gunawardena
>>> Sent: Wednesday, October 31, 2007 7:06 AM
>>> To: mashup-dev at wso2.org
>>> Subject: Re: [mashup-dev] jslint does not parse E4X - reports inline
>>> E4X code as fatal errors
>>>
>>> I think one option would be to provide validation as an option, but
>>> turned off by default. We can include the caveat that E4X will produce
>>> warnings which can be safely ignored, and not prevent the user from
>>> saving the script. I think this is better than having no option of
>>> validation at all, since at least a script without E4X can be safely
>>> validated.
>>>
>>> To go one step further, is there a safe way to check for the presence
>>> of
>>> E4X code (atleast the tags that lint complains about) before running
>>> the
>>> validation? If so, we can just skip the validation if E4X is present,
>>> so
>>> that scripts without any can benefit.
>>>
>>> In the mean time I guess we can also write to Mr. Crockford, who has
>>> actually asked on his page whether jslint is too strict, and explain
>>> the
>>> need for an option to make it not complain about E4X.
>>>
>>> Bye,
>>> Channa.
>>>
>>> Tyrell Perera wrote:
>>>       
>> Team,
>>
>> I recently integrated syntax validation before saving service JS
>>     
>>>> source
>>>>         
>> from the UI. However, I had to comment the changes out due to
>>     
>>>> $subject.
>>>>         
>> It looks like jslint does not support e4x. Since e4x is a critical
>> feature in the Mashup Server I would like to hear your suggestions on
>> whether to keep validation or remove it.
>>
>> Thanks,
>>
>> Tyrell
>>
>>
>> [1] http://www.jslint.com/lint.html
>>
>> --
>> Tyrell Perera
>> Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
>> email: tyrell at wso2.com; cell: +94 77 302 2505
>>
>> "Oxygenating the Web Service Platform."
>>     
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>   
>>>>
>>>>         
>>> --
>>> ********************************************
>>> Channa Gunawardena
>>> Technical Lead, WSO2 Inc.
>>> channa at wso2.com; Mobile: +94 71 306 2722
>>> "Oxygenating the Web Service Platform."
>>>
>>>
>>> _______________________________________________
>>> Mashup-dev mailing list
>>> Mashup-dev at wso2.org
>>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>>>       
>
>   
>> _______________________________________________
>> Mashup-dev mailing list
>> Mashup-dev at wso2.org
>> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>>     
>
>
> - --
> Tyrell Perera
> Senior Software Engineer; WSO2, Inc.; http://www.wso2.com/
> email: tyrell at wso2.com; cell: +94 77 302 2505
>
> "Oxygenating the Web Service Platform."
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHKLFXehFdPcgGx7oRAjrmAKDbej2J3/jF1E1CgjBValLrirJUIACg2jFE
> Oz6Hs6fwxnZvfwCgK4QCBd0=
> =NSA9
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Mashup-dev mailing list
> Mashup-dev at wso2.org
> http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
>
>