Salvador Ortiz > JSPL-1.07 > JSPL::Visitor

Download:
JSPL-1.07.tar.gz

Dependencies

Annotate this POD

CPAN RT

New  1
Open  2
View/Report Bugs
Source  

NAME ^

JSPL::Visitor - Perl things visiting JavaScript

DESCRIPTION ^

As described in "Round trip integrity" in JSPL all perl things that you pass by reference to JavaScript land conserve their identity, no matter how much they have travelled between both interpreters. Thats what you expect.

Upon entering JavaScript land they will become JavaScript objects, and as such they can be extended.

For example, your ARRAYs visiting JavaScript, as PerlArray instances, can be extended with some new non-numeric properties, and your perl subroutines, PerlSub instances, can get a 'prototype' property in its way to become constructors. That is the way JavaScript works.

Sometimes you need to break the transparency abstraction to known from perl land how your perl thing is being used on JavaScript.

When you call "jsvisitor" in JSPL::Context passing to it some reference that is visiting JavaScript you will get a JSPL::Visitor instance.

That objects allows you to inspect the perl value's wrapper object being used in JavaScript land.

INSTANCE METHODS ^

JSPL::Visitor instances inherits from JSPL::Object. See that page for details.

In addition, JSPL::Visitor object have the following:

VALID ( )

Returns TRUE if the instance is still valid, FALSE otherwise.

CAVEATS AND WARNINGS ^

A perl thing visiting JavaScript becomes a visitor when it enters JavaScript for the first time, but looses its visitor status as soon as JavaScript garbage collects it. That is, when the thing's wrapper object isn't referenced in a property anymore.

Perl values that you bind become a visitor as long as they are binded, but perl values that you pass as arguments for JavaScript functions calls are visitors only for the duration of the call, unless the function stores the reference somewhere.

JSPL::Visitor objects don't modify in any way the life cycle of the object nor the life cycle of the perl thing. if you hold a JSPL::Visitor for a long time, the object can be garbage collected in JavaScript, invalidating the JSPL::Visitor instance.

You should use only lexical variables in a well defined scope for JSPL::Visitor instances.

And unless you are playing "Alice in Wonderland", never pass to JavaScript a JSPL::Visitor. JSPL won't protect you for doing nasty things.

syntax highlighting: