2008/5/13 <[EMAIL PROTECTED]>: > > what about > http://wiki.ecmascript.org/doku.php?id=proposals:versioning > and > http://wiki.ecmascript.org/doku.php?id=discussion:versioning > > ? > > if I read those documents well > ES1-4 support backward-compatibility > > and later for ES5 etc. > we could either use > application/ecmascript;version=5 > > or the global > __MAX_ECMASCRIPT_VERSION__ > > or the pragma > use edition 5 >
On developer tools and mime-types, subversion will treat application/ecmascript as binary. http://subversion.tigris.org/faq.html#binary-files Subversion treats the following files as text: - Files with no svn:mime-type - Files with a svn:mime-type starting "text/" - Files with a svn:mime-type equal to "image/x-xbitmap" - Files with a svn:mime-type equal to "image/x-xpixmap" All other files are treated as binary, meaning that Subversion will: - Not attempt to automatically merge received changes with local changes during svn update or svn merge - Not show the differences as part of svn diff - Not show line-by-line attribution for svn blame
_______________________________________________ Es4-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es4-discuss
