On Wednesday, 11 November 2020 at 22:29:00 UTC, SealabJaster
wrote:
On Wednesday, 11 November 2020 at 22:10:38 UTC, WhatMeWorry
wrote:
Thanks. Would you or anyone reading this know if this is
unique to D or does C++ also behave like this? Also, where is
the memory, that new allocates? Is it i
On Wednesday, 11 November 2020 at 22:10:38 UTC, WhatMeWorry wrote:
Thanks. Would you or anyone reading this know if this is
unique to D or does C++ also behave like this? Also, where is
the memory, that new allocates? Is it in the heap (thought heap
was available only at runtime) or some othe
On Wednesday, 11 November 2020 at 22:10:38 UTC, WhatMeWorry wrote:
Also, where is the memory, that new allocates?
It is in the executable's static data block, just like if you
declared a static array in the global space.
I think this is D specific but I'm not sure about that.
On Wednesday, 11 November 2020 at 06:21:38 UTC, Jacob Carlborg
wrote:
On 2020-11-11 06:29, WhatMeWorry wrote:
Which begs the question, how would the statement, m_State =
new BreakState() ever get executed?
class DebuggerSession
{
private BreakState m_State = new BreakState();
privat
On 2020-11-11 06:29, WhatMeWorry wrote:
Which begs the question, how would the statement, m_State = new
BreakState() ever get executed?
class DebuggerSession
{
private BreakState m_State = new BreakState();
private UnrealCallback m_UnrealCallback;
this( )
{
}
//
