|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 documentation for YCP Builtins does not clarify "in a new context" | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Olaf Dabrunz <odabrunz> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | locilka |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
This is part of yast2-core/libycp "in a new block" now, fixed in svn trunk. |
In the YaST2 documentation for YCP Builtins at http://forgeftp.novell.com/yast/doc/SL10.2/tdg/Book-YaSTReference.html, the the phrase "in a new context" is used in several places. It is not really clear what this means. (My previous guess was that it means that the expression or block is executed in a scope of its own where it cannot change any program variables in other scopes, as it is done for functional programming languages. But I have been told already that this is not true. It rather means that only the variable for keys and values are "local" to the new context. Careful reading actually suggests that only the "loop variables" are "local" in the "new context". But it is not very clear.)