Topic awaiting preservation: is IE not capable of import export? (Page 1 of 1)

Apparently not... using them gives an automatic syntax error.

I don't totally need them, but it would've been nice.

Why must IE screw up all my wonderful plans?

Import Export? Can you be more precise, because I don't know what you're talking about...?

IE 6.0 and 6.0SP1 both import/export fine. I just exported everything before I reloaded a machine, then imported everything back in without a single problem.

I think IE screws up with your wonderful plan becuase it has a built function to wreck anything that might compete against MS in a future time and/or dimension

_________________________
Anyone who has lost track of time when using a computer knows the propensity to dream, the urge to make dreams come true and the tendency to miss lunch.
- copied from the wall of cell 408 -

you know... from different frames or windows you can export certain variables from one script and import them into another script.

export *; //exports all variables, functions, objects etc. from current script.

import item1, ..., itemN; //imports named variables or functions into script.
import *; // imports everything exported.

it was introduced in 1.2... we're up to what? .. 1.5 now.

I have never heard of that function before in my life. If it ever existed, it must have been an early Netscape creation that never made it into the ECMA spec.

If you need to access another frame or window's variables, get a variable that's a reference to that frame or window:

// for new windows
mywin = window.open(...);
// for frames
mywin = window.parent.frames[0].frames[1]; // might be "frame" instead of "frames," i forget

And then, once you have that reference, simply use it like so:

otherwindowsvariable = mywin.variable;
// for example:
mywin.document.write('hi');
mywin.document.close();

Note that you can only do this for windows that you have opened yourself or frames that contain pages on your own domain. This is a security restriction.

The poster has demanded we remove all his contributions, less he takes legal action.
We have done so.
Now Tyberius Prime expects him to start complaining that we removed his 'free speech' since this message will replace all of his posts, past and future.
Don't follow his example - seek real life help first.

well it is still in the ECMA script spec.

I liked it, i thought it would be cool to use... and it works in Mozilla....

Oh how smooth and clean it was working in mozilla when i first tried it....
yay!
Then IE came along ... yeah i knew other ways to do it... just playing with stuff.

I just searched my (admittedly somewhat old) PDF version of the ECMA-262 specs and the words "import" and "export" only appear in the list of future reserved words.

Also, I don't think these words *would* be in the ECMA spec, now that I think about it, because the way you're describing them they seem specific to web browsers, and the ECMA spec is more general than that (the ECMAscript functions that are specific to Javascript tend to be in the W3C specs).

Could you point me to a place where this syntax is defined? You said it worked in Mozilla, perhaps somewhere on the Mozilla page?

oh yeah it is not in the ECMA spec, my bad.
And you're right, it wouldn't be listed there.
I read too fast the statement "This feature is not in ECMA 262, Edition 3."

Kind of wierd though... with that "Edition 3" on the end, kind of threw off my comprehension of the context clues.

Anywho, yeah I found it on Netscapes Core JavaScript Reference 1.5 here.



[This message has been edited by genis (edited 10-04-2002).]