Browse Source

additional thoughts about passing arguments to source code blocks

Eric Schulte 16 years ago
parent
commit
cfcff524d0
1 changed files with 10 additions and 0 deletions
  1. 10 0
      rorg.org

+ 10 - 0
rorg.org

@@ -24,6 +24,12 @@ it's return result to a variable.  This would just add the ability to
 specify the values of the arguments to the source code block assuming
 any exist.  For an example see 
 
+When a variable appears in a header argument, how do we differentiate
+between it's value being a reference or a literal value?  I guess this
+could work just like a programming language.  If it's escaped or in
+quotes, then we count it as a literal, otherwise we try to look it up
+and evaluate it.
+
 ** TODO figure out how to handle graphic output
 This is listed under [[* graphical output][graphical output]] in out objectives.
 
@@ -608,6 +614,10 @@ inline source code blocks) [[file:test-export.org]]
 result
 #+end_src
 
+#+begin_src ruby :var num=9
+var + 4
+#+end_src
+
 
 * COMMENT Commentary
 I'm seeing this as like commit notes, and a place for less formal