Future of the Python Linux Distribution

[Alex]

> Not quite.  Part of the test is figuring out how to call the Rbbx()
> function.

Hmm, seems like it should be 

/rgt { _rbar exch get } bind def
/p4 { 4 { pop } repeat } bind def
/ism { { rgt } forall arcto p4 } bind def
/stuff { _rbar exch 3 -1 roll put } bind def
/Rbbx { gsave [ 6 1 roll ] /_rbar exch def
 3 rgt 1 rgt add 1 stuff 2 rgt 0 rgt add 0 stuff
 2 rgt 3 rgt 4 rgt add newpath M
 [ [ 2 1 0 1 4 ] [ 0 1 0 3 4 ] [ 0 3 2 3 4 ] [ 2 3 2 1 4 ] ]
 { ism } forall gsave Sg fill grestore
 Sg S stroke grestore } bind def
Rbbx
showpage

...but that is giving me this error:

Error: /rangecheck in --roll--
Operand stack:
   --nostringval--   6   1
Execution stack:
   %interp_exit () --nostringval-- --nostringval-- --nostringval-- false
   --nostringval-- --nostringval-- %runexec_finish --nostringval--
   --nostringval-- --nostringval-- --nostringval--
Dictionary stack:
   --dict:682/701--   --dict:0/20--   --dict:49/200--
Current allocation mode is local
Current file position is 417

...since it was a range check error, I thought maybe you could swap the
6 and the 1, but that gave the different error

Error: /rangecheck in --get--
Operand stack:
   --nostringval--   3

...dumping stuff on the stack prior to the call, like 
100 90 20 29 20 10 Rbbx 
didn't help, either, so I assume the implied "signature" of Rbbx (no
arguments) is accurate.

This-is-amusing'ly yrs Alex.