4 ms·

Languages are not the same, you'll never have interoperability; try exporting a .NET object with a 64-bit integer to be consumed by JavaScript, for example. Te

by Touche 11y ago

Languages are not the same, you'll never have interoperability; try exporting a .NET object with a 64-bit integer to be consumed by JavaScript, for example. Text wins.

UK-AL 11y ago
You would serialise it? $obj = [PSCustomObject]@{ Number = [long]2 } $obj | ConvertTo-Json
- Touche 11y ago
  Try with the number 9223372036854775807. Then try consuming this JSON in Node.
  - UK-AL 11y ago
    $obj = [PSCustomObject]@{ Number = [string]9223372036854775807 } $obj | ConvertTo-Json The lack of decent types, is surely a weakness of js?
orf 11y ago
You can have interoperability, COM does it well on Windows. JavaScript, .net, Python, ruby, C, C++ can all access COM methods and attributes.
13of40 11y ago
PS C:\> 0x1234567812345678 1311768465173141112 PS C:\> 0x1234567812345678 >.\foo.txt ; cat .\foo.txt 1311768465173141112 PS C:\> "WScript.Echo('$(0x1234567812345678)')" >.\foo.js ; cat .\foo.js ; cscript //nologo .\foo.js WScript.Echo(1311768465173141112) 1.31176846517314E+18 ... I'm not seeing your point.
- Touche 11y ago
  > I'm not seeing your point. JavaScript does not have 64-bit integers. So if you exported an object with 64-bit integers to XML, for example, a JavaScript program could not (correctly) deserialize that XML.
  - douche 11y ago
    Javascript doesn't really have integers, at all, so...