this may help to get the plain %request object:

k ^SPOOL s %io=$I O 2 u 2 ZW %request c 2 u %io

or whatever object you need to trace

YEAH, it's built for visual CSP pages

From Class Docs.:

Somewhere in the CSP page. This is just ~20% of the content

There are geographies in this world where a Decimal-Comma is used instead of a Decimal-Point.
Never met a Decimal-Pipe  😉 

Just received notice:

Provide a single page view of free space in IRIS DBs
has changed status to: Community Opportunity

Just to verify.

Status is:  "NEEDS REVIEW" for almost a month!  
I have a feeling.

I miss 4 points for the community idea for my Snapshot:
https://ideas.intersystems.com/ideas/DPI-I-799
It's also filled into OEX

To me, the most impressive fact about InterSystems is that it doesn't
hide or deny its roots or reject its history, and keep its backward compatibility.

I remember a customer who had composed and used an incredible complicated
program to create knitwear patterns with his equipment for over 30 years without change.
When he migrated to IRIS it was running perfectly without changing a single bit.

This still impresses me more than all the new language features
that force me to adjust versions as an ongoing challenge.

3 variants come to my mind

1. writing to ErrorLog  Do LOG^%ETN()
2.  write to Systrem message.log

    set %evgeny=$io
    open 1 use 1 write !,"Was in my REST code",! close 1
    use %evgeny

3. If you have a terminal session  LOCK  ^%EVGENY --- And into your code, add this simple loop 

4.  for  LOCK +^%EVGENY QUIT:$TEST   HANG 0.5

   Now your method loops, and you can attach with any external debugger. Releasing the LOCK from Terminal does the "un-freeze"

Simplified:  %CSP.Page is a collection of methods and event handlers without any own properties.
Related data are kept outside in %CSP.Request and %CSP.response.
But you may mimic InitialExpressions by using PARAMETERS 

Not really surprised. The Python version was in as the first anyhow

I understand that using the IRIS Native API is the important feature.
Is this also valid for IRIS Native API for ObjectScript ????.  
No doubt it is EXTERNAL on a different instance,
talking to the same interface as Java, NodeJS, Python, .NET
facing the same limitations  (Functions !)

From Class Docs:
• classmethod ExportAllClassesIndividual(dirname As %String = "", qspec As %String = "", ByRef errorlog As %String, Charset As %String = "", Package As %String = "*", SubDir As %Boolean = 0) as %Status

Export all the classes as individual XML files to a directory.

This method loops through all the classes, exporting each one as an individual XML file named after the classname to the directory dirname. If you specify a Package, then it exports only this package. If SubDir is true,, the method exports sub-packages as subdirectories.

Now the directory is your list of classes and equal sizes of files 
might most likely mean identical content. Or you do a text compare

You are right. $system.OBJ.Export~whatever is oriented to the Namespace

BUT:
There still seems to be no limitation to map a specific database file
to more than 1 namespace. e.g. USER and MERGER (here Read Only)
Then $system.OBJ.Export~whatever takes what it finds in MERGER.
It's quite a dirty approach and only meant for READING the code, therefore, ReadOnly

In any case, it's safer just to copy the (most likely static) DB of interest
and use it in MERGER
 

A great overview !

small add-on:  at 
https://hub.docker.com/u/intersystemsdc you find actually 53 community-licensed packages