Comment by Borg3

3 months ago

Holy moly.. Thread safety.. Good point and Bad point. I myself use threads sparsly, so I dont intermix calls between threads..

6 comments

Borg3

Reply
1718627440  3 months ago

It also has different behaviour in a single thread. This can be what you want though, but I would prefer it to pass that context as a parameter instead of having it in a hidden static variable.

  • Borg3  3 months ago

    What different behaviour you mean? static in function means that this is just preallocated somewhere in data, not on stack nor heap. Thats it. Yes, its not thread safe so should never be used in libraries for any buffering.

    But in program, its not bad. If I ever need multiple calls to it in same thread:

      static char buf[8][32];
  static int z;
  char *p=buf[z];
  z=(z+1)&7;

    Works pretty well ;)

    • 1718627440  3 months ago

      > What different behaviour you mean?

      Static foremost means that the value is preserved from the last function invocation. This is very different behaviour, than an automatically allocated variable. So calling a function with a static variable isn't idempotent, even when all global variables are the same.

      > If I ever need multiple calls to it in same thread:

      What is this code supposed to do???? It hands out a different pointer, the first 8 times, than starts from the beginning again? I don't see what this is useful for!

      3 replies →