@cmuratori @VinoBS We tried supporting that "properly", but it was ugly. There's a workaround where you #define STBIR_MALLOC to return temp.
-
-
Replying to @cmuratori
@cmuratori@VinoBS It requires two coupled calls, one to query how large the mem needed to be, one to do the resizing.2 replies 0 retweets 0 likes -
Replying to @nothings
@cmuratori@VinoBS With N variant resizing functions, need 2N total functions And you have to pass in two more parameters so that's uglier.1 reply 0 retweets 0 likes -
Replying to @nothings
@cmuratori@VinoBS So now you have to arbitrarily choose an easy/medium/hard-API threshhold for which functions support that and which don't1 reply 0 retweets 0 likes -
Replying to @nothings
@cmuratori@VinoBS Since the STBIR_MALLOC api can be used to supply temp memory trivially without coupling, and had to have that anyway,2 replies 0 retweets 0 likes -
Replying to @nothings1 reply 0 retweets 0 likes
-
Replying to @cmuratori
@cmuratori@VinoBS No, it's not.#define SBITR_MALLOC(context, size) context // pass in temp mem as context1 reply 0 retweets 0 likes -
Replying to @nothings2 replies 0 retweets 0 likes
-
Replying to @cmuratori
@cmuratori@VinoBS "you could just guess the size, etc"1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.