The change from TEST to Quality Assurance involves a process to remove debug code from the source code. this process is described in CodeReWrite.

Tables GC and ULTcase is dependent on the evolution of the Unicode and when new characters is added,then these tables has to change. But if this is done the whole package Y2018-Text has to be reassembled. Tools for generating GC and ULTcase here.

Procedures for debug purpose in Y2018-Text code

All debug is published to the active path (PWD) during the run to files named

1. “q” & Ada.Task_Identification.Image(Ada.Task_Identification.Current_Task) & ".lst"
2. “q” & Ada.Task_Identification.Image(Ada.Task_Identification.Current_Task) & "_alt.lst"

The prefix”q” is used for making it eazier to spot debug files.

This debug is built for use in a multi-process environment and the name must contain the name of the current task.
(Y2018.Text.TestQ)

Qinit(s:String) – will remove all regular files in the active path with a name beginning with ‘q’ and with the suffix ‘.lst’. After the removing of files a call of Qblock(s) is executed.

Qblock(s:String) – publish a box to the debug file with the parameter

Type ANKA is used for prefixing a debug row

• KALLE (or all calls without the ANKA type) – No prefix
• FNATTE – insert one TAB as prefix
• KNATTE – insert two TABs as prefix
• TJATTE – insert three TABs as prefix
• KAJSA – mark this row as important with "!]" & TAB as prefix
• KNASE – mark this row as temporary with ".]" & TAB as prefix
• BITTAN – donnot publish anything to any debug. Open and closes the debug file but donnot print anything.

When a new debug file is created it is ‘stamped’ with this command

Put_Line(fileOut,"TIMESTAMP " & GNAT.Time_Stamp.Current_Time)

to make it sure that the contents is from this run. Note that a new debug file is also created when the debug is in a new thread.

Qappend or Qappend_alt procedure calls prints to the actual debug file. Structure of the call

1. ANKA type value for prefixing (optional)
2. String type value, except CList maps
3. (other parameters)

• procedure Qappend(a:ANKA;s:String);
• procedure Qappend(a:ANKA;s:String;i1:Integer);
• procedure Qappend(a:ANKA;s:String;i1:Integer;i2:Integer);
• procedure Qappend(a:ANKA;s:String;b:Boolean);
• procedure Qappend(a:ANKA;s:String;i1:Integer;s1:String);
• procedure Qappend(a:ANKA;s:String;i1:Integer;i2:Integer;s2:String);
• procedure Qappend(a:ANKA;s:String;wws:CFix);
• procedure Qappend(a:ANKA;s:String;c:CodePoint;wws:CFix;f:Integer;l:Integer);
• procedure Qappend(a:ANKA;s:String;c:CodePoint);

Qappend and Qappend_alt with CList maps

procedure Qappend(map:in out Y2018.Text.Core.Str.Clist.Map;startRow:String:="";endRow:String:="";rowPrefix:String:="";keep:Boolean:=FALSE);
procedure Qappend(a:ANKA;map:in out Y2018.Text.Core.Str.Clist.Map;startRow:String:="";endRow:String:="";rowPrefix:String:="";keep:Boolean:=FALSE);

Example ExMy of output to a q____.lst file from Qappend's and Qinit.

Sometimes it is important to publish debug to another file, and this is the reason for the ‘_alt’ procedures.