Re: Disabling string evaluation in a logging system

["Jeffrey R. Carter" <spam.jrcarter.not@spam.acm.org>]

stefan-lucks@see-the.signature wrote:
> 
> package Flexi_Log is
> 
>   procedure Write(Log_Level: Log.Level_Type;
>                   Message_1: String := "";
>                   Message_2: String := "";
>                   Message_3: String := "";
>                   ...
>                   Message_9: String := "");
>   -- if Log_Level>0 then
>   --   Log.Write(Message_1 & Message_2 & ... , Log_Level);
>   -- end if;
> 
> end Flexi_Log;
> 
> In any case, the number of different strings to make one message is 
> constant. The constant is under your control, but it is constant. If your 
> support goes for up to, say, Message_9, a message for the log which 
> consists of 10 or more parts may still trouble you. So change the constant 
> sufficiently large that it doesn't trouble you too often ...

You could also do something like:

type Message_List is array (Positive range <>) of Ada.Strings.Unbounded;

procedure Write (Level : Log.Level_ID; Message : Message_List);
-- If Level > No_Logging and Message'Length > 0 then log the concatenation of
-- the strings in Message.

But I don't see that it buys you much, if anything.

Ultimately, this sounds like a case of premature optimization, given that the 
string operations are not impacting your timing requirements, according to 
another post.

-- 
Jeff Carter
"You've got the brain of a four-year-old boy,
and I bet he was glad to get rid of it."
Horse Feathers
47