From bae7b8d3abc15ce84448647b64b9bc701d143732 Mon Sep 17 00:00:00 2001
From: Sami Vaarala <sami.vaarala@iki.fi>
Date: Mon, 17 Mar 2014 23:34:34 +0200
Subject: [PATCH] ditz issue update

---
 ...6b0504aff1a6ef28b9d801d0f1303299bea2d.yaml | 13 ++++++++++++
 ...b500270dcd7b4a97139129722f727837d0f51.yaml | 20 +++++++++++++++++++
 ...3dcf6f2d8480504abb99079bed684a278cc13.yaml | 18 +++++++++++++++++
 3 files changed, 51 insertions(+)
 create mode 100644 bugs/issue-a25b500270dcd7b4a97139129722f727837d0f51.yaml
 create mode 100644 bugs/issue-d503dcf6f2d8480504abb99079bed684a278cc13.yaml

diff --git a/bugs/issue-3876b0504aff1a6ef28b9d801d0f1303299bea2d.yaml b/bugs/issue-3876b0504aff1a6ef28b9d801d0f1303299bea2d.yaml
index fabbd81f..605e7583 100644
--- a/bugs/issue-3876b0504aff1a6ef28b9d801d0f1303299bea2d.yaml
+++ b/bugs/issue-3876b0504aff1a6ef28b9d801d0f1303299bea2d.yaml
@@ -16,3 +16,16 @@ log_events:
   - sva <sami.vaarala@iki.fi>
   - created
   - ""
+- - 2014-03-17 21:22:08.533628 Z
+  - sva <sami.vaarala@iki.fi>
+  - commented
+  - |-
+    Logger name automatic detection would suffer from tail calls.  However,
+    because logger creation uses a constructor call there is no problem:
+    constructor calls currently block tail call handling.
+    
+    Similarly, the 'caller' non-standard property would not work properly
+    with tail calls.  But that feature disables tail calls altogether now,
+    so this problem won't be triggered.
+    
+    So, at the moment there are no known issues to document.
diff --git a/bugs/issue-a25b500270dcd7b4a97139129722f727837d0f51.yaml b/bugs/issue-a25b500270dcd7b4a97139129722f727837d0f51.yaml
new file mode 100644
index 00000000..8ddad147
--- /dev/null
+++ b/bugs/issue-a25b500270dcd7b4a97139129722f727837d0f51.yaml
@@ -0,0 +1,20 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: "duk_call_method: swap func and this binding order?"
+desc: |-
+  The order [ this func arg1 ... argN ] is often more convenience when
+  the 'func' is read from an object.
+type: :task
+component: duk
+release: v0.11
+reporter: sva <sami.vaarala@iki.fi>
+status: :unstarted
+disposition: 
+creation_time: 2014-03-16 22:09:31.034074 Z
+references: []
+
+id: a25b500270dcd7b4a97139129722f727837d0f51
+log_events: 
+- - 2014-03-16 22:09:31.194022 Z
+  - sva <sami.vaarala@iki.fi>
+  - created
+  - ""
diff --git a/bugs/issue-d503dcf6f2d8480504abb99079bed684a278cc13.yaml b/bugs/issue-d503dcf6f2d8480504abb99079bed684a278cc13.yaml
new file mode 100644
index 00000000..3056cb8b
--- /dev/null
+++ b/bugs/issue-d503dcf6f2d8480504abb99079bed684a278cc13.yaml
@@ -0,0 +1,18 @@
+--- !ditz.rubyforge.org,2008-03-06/issue 
+title: should separator for duk_join() be at the top?
+desc: ""
+type: :task
+component: duk
+release: v0.11
+reporter: sva <sami.vaarala@iki.fi>
+status: :unstarted
+disposition: 
+creation_time: 2014-03-16 21:04:43.748743 Z
+references: []
+
+id: d503dcf6f2d8480504abb99079bed684a278cc13
+log_events: 
+- - 2014-03-16 21:04:43.892574 Z
+  - sva <sami.vaarala@iki.fi>
+  - created
+  - ""