Expose the tag unescape and tags parsing under the IbisTags API

Review Request #3166 — Created May 7, 2024 and submitted

Information

ibis/ibis
default

Reviewers

Expose the tag unescape and tags parsing under the IbisTags API

Called in the turtles.

Summary ID
Expose the tag unescape and tags parsing under the IbisTags API
972b025becba3196b6a8c0ebf4f9bfb254bdf9d7
Description From Last Updated

will be returned

QuLogicQuLogic

Shouldn't this not happen because of the g_return_val_if_fail? (though I guess technically that could be optimized out)

QuLogicQuLogic

I do know it is set even with zero matches, but it wasn't clear from the docs if this is …

QuLogicQuLogic

One more test with invalid escape (e.g., \b->b as in the example from the spec)?

QuLogicQuLogic
grim
QuLogic
  1. 
      
  2. ibis/ibistags.h (Diff revision 2)
     
     
    Show all issues

    will be returned

  3. ibis/ibistags.c (Diff revision 2)
     
     
     
     
     
     
     
     
    Show all issues

    Shouldn't this not happen because of the g_return_val_if_fail? (though I guess technically that could be optimized out)

    1. You're right. That said we should probably allow empty string to be passed.

  4. ibis/ibistags.c (Diff revision 2)
     
     
    Show all issues

    I do know it is set even with zero matches, but it wasn't clear from the docs if this is set on error. So maybe this should use g_clear_pointer?

  5. ibis/tests/test_tags.c (Diff revision 2)
     
     
     
     
     
     
     
     
     
     
     
     
    Show all issues

    One more test with invalid escape (e.g., \b->b as in the example from the spec)?

    1. I agree, and we should also be doing the test\ test as well. However, these functions get made private in /r/3167/ so I'm not going to fix it here, but I will go and add the tests in the other rr.

  6. 
      
grim
QuLogic
  1. Ship It!
  2. 
      
grim
Review request changed
Status:
Completed