Re: About String

> I meant to say
> 
>    procedure Patati_Patata is
>    begin
>       begin
>          declare
>             S : String := A_Function_Raising_Constraint_Error;
>          begin
>             --  some code
>          end;
>       exception
>          when Constraint_Error =>
>             --  deal with the problem ..
>       end;
>       --  .. and carry on
>    end;

And it's what exactly I don't think pretty nice and easy to maintain.
Other 
solution proposed by previous post is to separate the code with nested
function:

procedure Patati_Patata is

    function Manage_S return String;

    function Manage_S return String is
    begin
       declare
          S : String := A_Function_Raising_Constraint_Error;
       begin
          --  some code
          return S;
       end;
    exception
       when Constraint_Error =>
          --  deal with the problem ..
          return ""; --  Or something else to manage the error but
something 
must be returned to be consistent
    end;

    S: String := Manage_S;

begin
    --  .. and carry on
end;

I think it's a better way especially because:
1) You can put away the nested function (for instance as a private package
function)
2) You can reuse the function
3) You string are constant most of time (meaning: "S: constant String :=
Manage_S;")

The only disadvantage for me is that you write a lot little function if
you use 
a lot of string (and frankly, you always do in high level application).

I wonder too if there is a nice way to manipulate string using access
type. I 
don't choose to try this way because I think it's the better way to
introduce 
some memory link.

Sebastien