| … | |
… | |
| 395 | =back |
395 | =back |
| 396 | |
396 | |
| 397 | =head2 Extension Objects |
397 | =head2 Extension Objects |
| 398 | |
398 | |
| 399 | Every perl extension is a perl class. A separate perl object is created |
399 | Every perl extension is a perl class. A separate perl object is created |
| 400 | for each terminal and each extension and passed as the first parameter to |
400 | for each terminal, and each terminal has its own set of extenion objects, |
| 401 | hooks. So extensions can use their C<$self> object without having to think |
401 | which are passed as the first parameter to hooks. So extensions can use |
| 402 | about other extensions, with the exception of methods and members that |
402 | their C<$self> object without having to think about clashes with other |
|
|
403 | extensions or other terminals, with the exception of methods and members |
| 403 | begin with an underscore character C<_>: these are reserved for internal |
404 | that begin with an underscore character C<_>: these are reserved for |
| 404 | use. |
405 | internal use. |
| 405 | |
406 | |
| 406 | Although it isn't a C<urxvt::term> object, you can call all methods of the |
407 | Although it isn't a C<urxvt::term> object, you can call all methods of the |
| 407 | C<urxvt::term> class on this object. |
408 | C<urxvt::term> class on this object. |
| 408 | |
409 | |
| 409 | It has the following methods and data members: |
410 | It has the following methods and data members: |
