W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2015

[Bug 27918] New: serialization output for functions

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Jan 2015 11:50:27 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-27918-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27918

            Bug ID: 27918
           Summary: serialization output for functions
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Serialization 3.1
          Assignee: cmsmcq@blackmesatech.com
          Reporter: r.stapper@lijbrandt.nl
        QA Contact: public-qt-comments@w3.org

Hi,

I'm very pleased with the adaptive serialization outputmethod( see related
item: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27498). However the output
for functions is very minimal (I'm using Basex however I don't think it's
Basex-specific).

When using closure-functions as internal datarecords (as I do) debugging
XQuery-code is a real brain-teaser. Some more informationIt would be very
wellcome. For example as Basex's map:serialization output for functions as
mapvalue, see example below:

xquery:
=======
let $f := function( $a, $b){ function( $f){ $f( $a, $b)}}
let $a := $f( 'a', 'b')
return map:serialize( map { "D" : $a})

result:
=======
{
  "D": function($f_9) as item()* { $f_9("a", "b") }
}

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 28 January 2015 11:50:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 28 January 2015 11:50:29 UTC