Thread: Hi, Curly brackets in a function call? What's that all about :)

I'm feeling a bit dodgy tonight so I've resolved the only sensible thing to do is press on with learning code lol! So I'm asking the question stated in the title. Check this code out:

Code:

void SetWindow(CoreWindow const& window)
{

.....some time later

Code:

    window.Activated({ this, &App::OnWindowActivationChanged });

    window.SizeChanged({ this, &App::OnWindowSizeChanged });

    window.Closed({ this, &App::OnWindowClosed });

};

All those function calls (which is what I think they are or are they data members?) are having standard brackets with these curly brackets inside them. I'm amazed this doesn't throw the compiler.

Is this code like making structs on the fly and passing them to function calls or something? It's totally new to me to see this, thanks

Hello chaps!

Thanks much for the replies really, really good cheers!

The code is taken from here it's the microsoft sorta tutorial on making a simple game in visual studio using DirectX12, afaik it is C++ as it states that in the lesson prior to this one.

Define the game's UWP app framework - UWP applications | Microsoft Docs

Thanks

Well then what a topic this has been. I did some research and here's what I found.

Firstly I went and researched what a list initialiser is, and it sure broadened my knowledge. The examples I worked through were with structs and using constructors for structs in the definition. I didn't even know you could do that lol! I got to see where a default constructor and a member initialiser could both be in a struct and depending on how the struct was created either one or the other would run.

Was really cool, even fun!

I also opened up Code::Blocks and started poking around some Microsoft files for windows. I prefer CB's search facility I can never get on with the one in VS 2015 (or just haven't learned to use it properly yet.

Well anyways....eventually I found this:

Code:

ITypedEventHandler<ABI::Windows::UI::Core::CoreWindow*, ABI::Windows::UI::Core::WindowActivatedEventArgs*> : ITypedEventHandler_impl<ABI::Windows::Foundation::Internal::AggregateType<ABI::Windows::UI::Core::CoreWindow*, ABI::Windows::UI::Core::ICoreWindow*>, ABI::Windows::Foundation::Internal::AggregateType<ABI::Windows::UI::Core::WindowActivatedEventArgs*, ABI::Windows::UI::Core::IWindowActivatedEventArgs*>>

Now to be clear this is referenced many times in the file and I mostly have no idea what it's doing (this is rather beyond my coding ken at this time) but it did at least appear as though in a very sophisticated way the function expects two arguments. One seems to be a pointer to the window and the other a pointer to the event arguments. It appears these are also almost defined in a way in the same line but that's a bit too much for me to understand at this time.

I thought you'd appreciate the feedback. For me however I'm in over my head now as that's a bit too much for me for to understand beyond only the gist of it. Thanks