Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
tutorials:advanced:task_trees [2015/07/09 11:32] – Updated ptr-cram-function lambda list handling. mpomarlantutorials:advanced:task_trees [2015/07/09 15:13] – [Using projection runs to guide plan transformation] mpomarlan
Line 284: Line 284:
 <code lisp> <code lisp>
 (swank:operate-on-system-for-emacs "cram-projection" (quote load-op)) (swank:operate-on-system-for-emacs "cram-projection" (quote load-op))
-(cram-projection:define-projection-environment example-env) 
 (in-package :cpl-impl) (in-package :cpl-impl)
 +(cram-projection:define-projection-environment example-env)
  
 (def-top-level-cram-function tryprj ()  (def-top-level-cram-function tryprj () 
Line 386: Line 386:
 </code> </code>
  
-Currently, by default the :ptr-parameter to cpl-impl:replace-task-code is nil, so when modifying a ptr-cram-function make sure to put a reasonable value there. (TODO: replace the default nil with the current effective compile-time parameter for the modified node.)+By default the :ptr-parameter to cpl-impl:replace-task-code is set to the previously effective value of ptr-parameter that is stored in the task tree node. This either the ptr-parameter in the code slot of the node (if there are no code replacements), or the ptr-parameter in the car object in the code-replacements list of the node. When a task tree node is created and a ptr-parameter is not specified, the default is nil.
  
 In our example here, the compile-time parameter is a string. It can however be anything, including a struct or a list, for when you need to pass on several objects through plan transformation. In our example here, the compile-time parameter is a string. It can however be anything, including a struct or a list, for when you need to pass on several objects through plan transformation.