great, thanks!
ddbg v0.0.4.5 makes use of this.

FYI, it works like this:
right after the process has been created (before it's started), ddbg
looks for an export "_main" and sets a breakpoint on it's start address.
when that one is hit, it looks for "_cr_trapExceptions" and
"_no_catch_exceptions" exports and sets them accordingly, if found.

Sean Kelly wrote:
> Sean Kelly wrote:
>>
>> So the debugger would set cr_trapExceptions=false before C main is even executed?  Okay, I can change that.
> 
> Done.  Changing cr_trapExceptions now only has an effect if done before C main is called, just like the flag in Phobos.
> 
> 
> Sean

setting single variables actually isn't that much work.
the current expression parser produces a memory chunk plus it's type.
so what's left is doing that twice (for lvalue and rvalue), checking
whether the types are identical and then copying one chunk over the other.
maybe i can get this into v0.0.5.

your example would become
set point.x = 5
set point.y = 77

torhu wrote:
> Jascha Wetzel wrote:
>> i can't possibly
>> think of anything else ddbg could ever need the curly brackets for. to
>> be sure we could also use something else:
>> §cast§
>> #cast#
>> :)
> 
> What if ddbg sometime in the future allows you to set the value of a struct by using a struct literal?
> 
> set point = { 5, 77 }
> 
> Might be a while until that feature materializes, but who knows. Setting variables during debugging comes in handy sometimes.