curiously, when running in the editor or when compiling with p-code, exiting the subroutine with an overlocked array seems to resolve the locking issue, whereas native code will raise error 10 upon exiting the sub. both will raise error 10 if the overlocked array is redim'd or erased within the sub.

you would mainly use a goto in this instance to continue to the next iteration of a loop since vb6 lacks a "continue" keyword. what makes this a bug imo is that if you use an "Exit Sub" or raise an exception, the lock count is decremented properly.

Could make an event out of it and share the brick for efficiency. It'd be like VidCon with high velocity masonry.

I'd actually probably use websockets unironically

server dead, rip

CIH-themed toblerone where if you eat it on april 26th you die instantly

happy birthday! hope you have a good one :]

marginally adequate online username, absolutely unusable as a foundation for any real life identity lmfao

been ~12 years since "toxoid49b", a testament to why you shouldn't let 13 year olds name things

I wrote my own open addressing hashmap with simple string keys and variant values and the performance increased by an order of magnitude when compiled. Turns out hammering the exception handler multiple times every time I reference a variable or command was bad for performance. What a concept.

It's technically not a problem since the whole project is getting shoved into an Excel spreadsheet at the end, but just. what

not complaining to be clear, it's just kinda ironic

going pretty good! hope you, fizz and co are doing well :]