 |
|
|
On Mar 31, 2006, at 22:45, Elliotte Harold wrote:
> Robin Berjon wrote:
>> Do you have an example of something in the DOM that hurts Java
>> that was obviously done so that Javascript would work? In the
>> other direction, you don't need to look any further than NodeList
>> (not even counting the liveness).
>
> Of course. No method overloading. Think createElement,
> createElementNS, etc. Java and C++ wouldn;t desing an API like that.
That's a red herring, you can trivially switch on arguments.length. I
think that whatever constraints that brought them to do this were
different. I'm not the OMG IDL specialist but could the overloading
issues come from there? It has quite a few dragons that have bitten
me in the past, notably concerning case-sensitivity.
--
Robin Berjon
Senior Research Scientist
Expway, http://expway.com/
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
