Why ExternalCalls is a MUST now for malloc?

Previously, with Island, I can directly call free, malloc

but now with .2533, I have to explicitly use ExternalCalls.free, ExternalCalls.malloc

Is this an intentional change? @ck

Probably the global methods got made private by mistake. Will fix, thanx.