aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorArun Isaac2021-07-05 15:47:07 +0530
committerArun Isaac2021-07-05 15:47:07 +0530
commit5d2368bad49a2663b9753bf559dc28caedb6aea6 (patch)
tree88c96637a21af1f441699b3f6c967f371732983a /doc
parent1880f7a2fed157220dd485f9e8ccd9f546996978 (diff)
downloadccwl-5d2368bad49a2663b9753bf559dc28caedb6aea6.tar.gz
ccwl-5d2368bad49a2663b9753bf559dc28caedb6aea6.tar.lz
ccwl-5d2368bad49a2663b9753bf559dc28caedb6aea6.zip
doc: Inline code snippets.
* doc/ccwl.skb (Tutorial)[Important concepts]: Inline code snippets.
Diffstat (limited to 'doc')
-rw-r--r--doc/ccwl.skb5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/ccwl.skb b/doc/ccwl.skb
index 80ed7c1..41b1642 100644
--- a/doc/ccwl.skb
+++ b/doc/ccwl.skb
@@ -54,9 +54,8 @@ has been run. Hence, we say that it is statically typed.]))
(p [In many languages, the order of arguments passed to a
function is significant. The position of each argument determines
which formal argument it gets mapped to. For example, passing
-positional arguments in Scheme looks like])
- (prog :line #f [(foo 1 2)])
- (p [However, in a language that supports named arguments (say,
+positional arguments in Scheme looks like ,(code "(foo 1
+2)"). However, in a language that supports named arguments (say,
Scheme or Python), the order of arguments is not significant. Each
argument explicitly names the formal argument it gets mapped to. For
example, in Scheme, passing named arguments may look like ,(code "(foo