Accessing the global object

[Bob]

Is there anyway to access the global object from inside a function other
than doing a "var _global = this;" before declaring the function?

Thanks

[Joost Diepenmaat]

"Bob" <no****@nowhere .comwrites:

Is there anyway to access the global object from inside a function other
than doing a "var _global = this;" before declaring the function?

If you know the name of the global and you're sure you're not overriding
the name, you can use the global name.

IWO, yes and no.

--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/

[Peter Michaux]

On Feb 21, 5:10 pm, "Bob" <nob...@nowhere .comwrote:

Is there anyway to access the global object from inside a function other
than doing a "var _global = this;" before declaring the function?

In a web browser the global object is usually available as a property
"window" of the global object. I think your idea of creating your own
"_global" is better. In ECMAScript 4 there will be a default "global"
property of the global object that references the global object. It
will work like "window" but "window" is a bad name when scripting in a
non-browser host.

Peter

[Richard Cornford]

Bob wrote:

Is there anyway to access the global object from inside a
function other than doing a "var _global = this;" before
declaring the function?

In javascript the value of the - this - keyword is determined by how a
function is called. If the function is not called as a method of an object
the value of the - this - keyword defaults to a reference to the global
object. As a result, from any context you can get a reference to the global
object using:-

function x(){
...
var localGlobalRef = function(){retu rn this;}();
...
}

This is 100% reliable in ECMAScript 3rd Ed. implementations , and quite
useful, but it looks like ES 4 will not be back-compatible with ES 3 in this
regard. Still, not being back-compatible with ES 3 may (fingers crossed) be
enough to kill ES 4 in its cradle so maybe that is not worth worrying about.

Richard.

[Bob]

Interesting. Is there anyway to distinguish ES3 from ES4, and if ES4 is
present then return the global property?

Thanks very much
"Richard Cornford" <Ri*****@litote s.demon.co.ukwr ote in message
news:fp******** ***********@new s.demon.co.uk.. .

Bob wrote:

>Is there anyway to access the global object from inside a
function other than doing a "var _global = this;" before
declaring the function?

In javascript the value of the - this - keyword is determined by how a
function is called. If the function is not called as a method of an object
the value of the - this - keyword defaults to a reference to the global
object. As a result, from any context you can get a reference to the
global
object using:-

function x(){
...
var localGlobalRef = function(){retu rn this;}();
...
}

This is 100% reliable in ECMAScript 3rd Ed. implementations , and quite
useful, but it looks like ES 4 will not be back-compatible with ES 3 in
this
regard. Still, not being back-compatible with ES 3 may (fingers crossed)
be
enough to kill ES 4 in its cradle so maybe that is not worth worrying
about.

Richard.

[AKS]

On Feb 22, 2:54 pm, "Richard Cornford" <Rich...@litote s.demon.co.uk>
wrote:

but it looks like ES 4 will not be back-compatible with ES 3 in this
regard. Still, not being back-compatible with ES 3 may (fingers crossed) be
enough to kill ES 4 in its cradle so maybe that is not worth worrying about.

Will be this compatible with ES4?

var localGlobalRef = (function () { return this; }).call(null);

[Thomas 'PointedEars' Lahn]

Peter Michaux wrote:

On Feb 21, 5:10 pm, "Bob" <nob...@nowhere .comwrote:

>Is there anyway to access the global object from inside a function
other than doing a "var _global = this;" before declaring the function?

In a web browser the global object is usually available as a property
"window" of the global object.

Nonsense. You are jumping to conclusions.

I think your idea of creating your own "_global" is better.

See <47************ **@PointedEars. de>, among others.

In ECMAScript 4 there will be a default "global" property of the global
object that references the global object.

I am looking forward to that.

It will work like "window" but "window" is a bad name when scripting in a
non-browser host.

However, how is the issue of accessing properties of the Global Object of
another global execution context going to to be addressed, as with frames
and windows?
PointedEars
--
var bugRiddenCrashP ronePieceOfJunk = (
navigator.userA gent.indexOf('M SIE 5') != -1
&& navigator.userA gent.indexOf('M ac') != -1
) // Plone, register_functi on.js:16

[Peter Michaux]

On Feb 23, 5:37 pm, Thomas 'PointedEars' Lahn <PointedE...@we b.de>
wrote:

Peter Michaux wrote:

On Feb 21, 5:10 pm, "Bob" <nob...@nowhere .comwrote:

Is there anyway to access the global object from inside a function
other than doing a "var _global = this;" before declaring the function?

In a web browser the global object is usually available as a property
"window" of the global object.

Nonsense. You are jumping to conclusions.

The word "usually" usually indicates one is not making a definitive
conclusion.

I think your idea of creating your own "_global" is better.

See <47C0C97C.5010. ..@PointedEars. de>, among others.

In ECMAScript 4 there will be a default "global" property of the global
object that references the global object.

I am looking forward to that.

It will work like "window" but "window" is a bad name when scripting in a
non-browser host.

However, how is the issue of accessing properties of the Global Object of
another global execution context going to to be addressed, as with frames
and windows?

this.opener

this.parent

this.frames

Peter

[Peter Michaux]

On Feb 24, 3:20 am, Thomas 'PointedEars' Lahn <PointedE...@we b.de>
wrote:

Peter Michaux wrote:

[...] Thomas 'PointedEars' Lahn [...] wrote:

Peter Michaux wrote:
On Feb 21, 5:10 pm, "Bob" <nob...@nowhere .comwrote:
Is there anyway to access the global object from inside a function
other than doing a "var _global = this;" before declaring the function?
In a web browser the global object is usually available as a property
"window" of the global object.
Nonsense. You are jumping to conclusions.

The word "usually" usually indicates one is not making a definitive
conclusion.

The word "usually" implies a perceived majority of cases where said
condition would apply.

Then I said what I meant. The overwhelming majority of JavaScript
hosts on earth are web browsers that have the global "window"
property.

>In ECMAScript 4 there will be a default "global" property of the global
object that references the global object.
I am looking forward to that.

>It will work like "window" but "window" is a bad name when scripting in a
non-browser host.
However, how is the issue of accessing properties of the Global Object of
another global execution context going to to be addressed, as with frames
and windows?

this.opener

this.parent

this.frames

That would imply ECMAScript Edition 4 is going to standardize properties of
Window host objects as built-in properties of the Global Object

I don't see a problem. As far as I know, they aren't standardizing the
properties of the global object, they are simply standardizing a way
to access the global object that can be sensibly used in a non-browser
host.

[snip <--- look Thomas, I snipped]

By the way, http://pointedears.de/scripts/ is still an error page.

Peter

[Peter Michaux]

On Feb 24, 10:36 am, Thomas 'PointedEars' Lahn <PointedE...@we b.de>
wrote:

Peter Michaux wrote:

[...] Thomas 'PointedEars' Lahn [...] wrote:

Peter Michaux wrote:
[...] Thomas 'PointedEars' Lahn [...] wrote:
Peter Michaux wrote:
On Feb 21, 5:10 pm, "Bob" <nob...@nowhere .comwrote:
Is there anyway to access the global object from inside a function
other than doing a "var _global = this;" before declaring the function?
In a web browser the global object is usually available as a property
"window" of the global object.
Nonsense. You are jumping to conclusions.
The word "usually" usually indicates one is not making a definitive
conclusion.
The word "usually" implies a perceived majority of cases where said
condition would apply.

Then I said what I meant. The overwhelming majority of JavaScript
hosts on earth are web browsers that have the global "window"
property.

Then I'm afraid your argument is a fallacious one indeed.

You've said things like this many times. As far as I know you have not
ever listed where these other billions of user agents are that are
not web browsers similar to IE4+/NN4+. Who/What/Where/Why/When/How are
they?

Peter