there are some proplems with fio_str_tmp function about facil.io HOT 3 CLOSED

Hi @immortalChensm ,

Thank you for opening this issue.

This is a design issue, solved in the 0.8.x branch, where the fiobj_str_tmp function is deprecated in favor of a macro based solution that allows multiple temporary strings to be placed on the stack.

Under the current design, the fiobj_str_tmp returns a thread-safe static variable. It is limited to a single temporary string per thread.

As it stands, there is no way to fix the fiobj_str_tmp function.

I agree with you that this design is suboptimal and so, it was deprecated.

However, allocating a string with fiobj_str_new should be fast enough... even if you need to remember to free the string with fiobj_free.

I hope this helps.

Kindly,
Bo.

from facil.io.

P.S. - I closed this issue because it's solved in 0.8.0 (pre-beta).

Thank you again for opening the issue.
Bo.

from facil.io.

Thank you very much for your reply. I see

from facil.io.