On Friday, 13 August 2021 at 21:36:35 UTC, Ruby The Roobster
wrote:
Thank you very much. The program runs successfully now.
You've got another potential issue you should be aware of. You've
name a member of your `Skeleton` as `init`. This may cause issues
at some point, as every type in
On Friday, 13 August 2021 at 21:10:38 UTC, Steven Schveighoffer
wrote:
Well, subtracting the length doesn't do much, you aren't
actually accessing the array block, you are just changing the
reference (which lives in thread-local storage). I kind of feel
like the whole entity table thing is
On Friday, 13 August 2021 at 21:10:38 UTC, Steven Schveighoffer
wrote:
On 8/13/21 3:59 PM, Mike Parker wrote:
On Friday, 13 August 2021 at 16:18:06 UTC, Ruby The Roobster
wrote:
...
...
...
Well, subtracting the length doesn't do much, you aren't
actually accessing the array block, you
On Friday, 13 August 2021 at 19:59:46 UTC, Mike Parker wrote:
You aren't supposed to be manipulating GC-managed memory via
class destructors. You can not rely on that memory being valid
at the time that it's accessed in the destructor---the object
may already have been destroyed.
On 8/13/21 3:59 PM, Mike Parker wrote:
On Friday, 13 August 2021 at 16:18:06 UTC, Ruby The Roobster wrote:
Context for this: I am creating a module of my own, and this is a
class contained in the module. You will notice that after calling
this class' constructor anywhere in a Win32 API
On Friday, 13 August 2021 at 16:18:06 UTC, Ruby The Roobster
wrote:
Context for this: I am creating a module of my own, and this
is a class contained in the module. You will notice that after
calling this class' constructor anywhere in a Win32 API
program, that the program doesn't close
On Friday, 13 August 2021 at 03:05:22 UTC, Mike Parker wrote:
On Friday, 13 August 2021 at 00:30:59 UTC, Ruby The Roobster
wrote:
When I run the program and close the window, the program still
runs in background mode. I don't know why this happens nor
how to fix it. Does anybody know
On Friday, 13 August 2021 at 03:05:22 UTC, Mike Parker wrote:
On Friday, 13 August 2021 at 00:30:59 UTC, Ruby The Roobster
wrote:
When I run the program and close the window, the program still
runs in background mode. I don't know why this happens nor
how to fix it. Does anybody know
On Friday, 13 August 2021 at 03:05:22 UTC, Mike Parker wrote:
On Friday, 13 August 2021 at 00:30:59 UTC, Ruby The Roobster
wrote:
When I run the program and close the window, the program still
runs in background mode. I don't know why this happens nor
how to fix it. Does anybody know
On Friday, 13 August 2021 at 00:30:59 UTC, Ruby The Roobster
wrote:
When I run the program and close the window, the program still
runs in background mode. I don't know why this happens nor how
to fix it. Does anybody know what's going on?
frame beat me to it, but it may well be that
On Friday, 13 August 2021 at 00:30:59 UTC, Ruby The Roobster
wrote:
When I run the program and close the window, the program still
runs in background mode. I don't know why this happens nor how
to fix it. Does anybody know what's going on?
AFAIK GetMessage() may return -1 if some error
11 matches
Mail list logo
