[M3devel] r_test, pr_test, pb_test

[Olaf Wagner]

Quoting Jay K <jay.krell at cornell.edu>:

> Olaf, I think pr_test and pb_test are cryptic, and there is
> no explanation what "pr" and "pb" stand for (as opposed
> to p_test, e_test, c_test, which have comment).
>
> I propose
>
> run_flags_test
> build_flags_test
>
> or
>
> program_with_run_flags
> program_with_build_flags
> program_with_compiler_flags
>
> or somesuch.
>
> I'm guessing "r" means "run flags", "b" means "build flags.
>
> I'll probably do something here very soon, since I'm adding another
> type of test.

Yes. I must have forgotten to document it better. They are there to run
a program or its build with additional flags or options.

You can easily see their use at the test instances though:

pr_test ("p2", "p213", "runtime arguments: @M3paranoidgc", "@M3paranoidgc")
pr_test ("p2", "p214", "runtime arguments: @M3noincremental",  
"@M3noincremental")
pr_test ("p2", "p215", "runtime arguments: @M3nogenerational",  
"@M3nogenerational")
pr_test ("p2", "p216", "runtime arguments: @M3nogc", "@M3nogc")

pb_test ("p2", "p217", ".M3SHIP program", "-no-m3ship-resolution")
pb_test ("p2", "p218", ".M3SHIP Program", "-no-m3ship-resolution")
pb_test ("p2", "p219", ".M3SHIP Program group-writable",  
"-no-m3ship-resolution -group-writable")
pb_test ("p2", "p220", ".M3SHIP library", "-no-m3ship-resolution")
pb_test ("p2", "p221", ".M3SHIP Library", "-no-m3ship-resolution")
pb_test ("p2", "p222", ".M3SHIP Library", "-no-m3ship-resolution  
-group-writable")
% The following test won't run until FSUtils.RmRec() is fixed
%pb_test ("p2", "p223", ".M3SHIP Library", "-no-m3ship-resolution  
-group-writable")

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194