Mercurial > emacs
comparison man/idlwave.texi @ 46918:82d113655734
Minor spelling and grammar corrections.
author | Paul Eggert <eggert@twinsun.com> |
---|---|
date | Fri, 16 Aug 2002 06:29:40 +0000 |
parents | 9059071c4fa9 |
children | 0e5a022947e9 |
comparison
equal
deleted
inserted
replaced
46917:7f23d458e897 | 46918:82d113655734 |
---|---|
1082 | 1082 |
1083 When you ask for routine information about an object method, and the | 1083 When you ask for routine information about an object method, and the |
1084 method exists in several classes, IDLWAVE queries for the class of the | 1084 method exists in several classes, IDLWAVE queries for the class of the |
1085 object, unless the class is already known through a text property on the | 1085 object, unless the class is already known through a text property on the |
1086 @samp{->} operator (@pxref{Object Method Completion and Class | 1086 @samp{->} operator (@pxref{Object Method Completion and Class |
1087 Ambiguity}), or by having been explicity included in the call | 1087 Ambiguity}), or by having been explicitly included in the call |
1088 (e.g. @code{a->myclass::Foo}). | 1088 (e.g. @code{a->myclass::Foo}). |
1089 | 1089 |
1090 @cindex Calling sequences | 1090 @cindex Calling sequences |
1091 @cindex Keywords of a routine | 1091 @cindex Keywords of a routine |
1092 @cindex Routine source information | 1092 @cindex Routine source information |
1592 allows a single call @code{obj->SetProperty} to set properties up the | 1592 allows a single call @code{obj->SetProperty} to set properties up the |
1593 entire class inheritance chain. This is often referred to as | 1593 entire class inheritance chain. This is often referred to as |
1594 @emph{chaining}, and is characterized by chained method calls like | 1594 @emph{chaining}, and is characterized by chained method calls like |
1595 @w{@code{self->MySuperClass::SetProperty,_EXTRA=e}}. | 1595 @w{@code{self->MySuperClass::SetProperty,_EXTRA=e}}. |
1596 | 1596 |
1597 IDLWAVE can accomodate this special synergy between class and keyword | 1597 IDLWAVE can accommodate this special synergy between class and keyword |
1598 inheritance: if @code{_EXTRA} or @code{_REF_EXTRA} are detected among a | 1598 inheritance: if @code{_EXTRA} or @code{_REF_EXTRA} are detected among a |
1599 method's keyword parameters, all keywords of superclass versions of the | 1599 method's keyword parameters, all keywords of superclass versions of the |
1600 method being considered are included in completion. The completion | 1600 method being considered are included in completion. The completion |
1601 buffer will label keywords based on their originating class. The | 1601 buffer will label keywords based on their originating class. The |
1602 variable @code{idlwave-keyword-class-inheritance} can be used to | 1602 variable @code{idlwave-keyword-class-inheritance} can be used to |
2051 @cindex Documentation header | 2051 @cindex Documentation header |
2052 @cindex DocLib header | 2052 @cindex DocLib header |
2053 @cindex Modification timestamp | 2053 @cindex Modification timestamp |
2054 @cindex Header, for file documentation | 2054 @cindex Header, for file documentation |
2055 @cindex Timestamp, in doc header. | 2055 @cindex Timestamp, in doc header. |
2056 @cindex Changelog, in doc header. | 2056 @cindex ChangeLog, in doc header. |
2057 | 2057 |
2058 @kindex C-c C-h | 2058 @kindex C-c C-h |
2059 @kindex C-c C-m | 2059 @kindex C-c C-m |
2060 The command @kbd{C-c C-h} inserts a standard routine header into the | 2060 The command @kbd{C-c C-h} inserts a standard routine header into the |
2061 buffer, with the usual fields for documentation (a different header can | 2061 buffer, with the usual fields for documentation (a different header can |
2625 time (as long as the shell is running), and are very useful when | 2625 time (as long as the shell is running), and are very useful when |
2626 execution is stopped in a buffer due to a triggered breakpoint or error, | 2626 execution is stopped in a buffer due to a triggered breakpoint or error, |
2627 or while composing a long command in the IDLWAVE shell. In the latter | 2627 or while composing a long command in the IDLWAVE shell. In the latter |
2628 case, the command is sent to the shell and its output is visible, but | 2628 case, the command is sent to the shell and its output is visible, but |
2629 point remains unmoved in the command being composed --- you can inspect | 2629 point remains unmoved in the command being composed --- you can inspect |
2630 the contituents of a command you're building without interrupting the | 2630 the constituents of a command you're building without interrupting the |
2631 process of building it! You can even print arbitrary expressions from | 2631 process of building it! You can even print arbitrary expressions from |
2632 older input or output further up in the shell window --- any expression, | 2632 older input or output further up in the shell window --- any expression, |
2633 variable, number, or function you see can be examined. | 2633 variable, number, or function you see can be examined. |
2634 | 2634 |
2635 If the variable @code{idlwave-shell-separate-examine-output} is | 2635 If the variable @code{idlwave-shell-separate-examine-output} is |