Make the global port a "weak" port.

Make the global port a "weak" port.

We could have just removed all references to the lazyPort, but this CL
prepares for using the lazyPort as controlPort.

BUG= http://dartbug.com/14461
R=lrn@google.com, ngeoffray@google.com

Committed: https://code.google.com/p/dart/source/detail?r=30938

[ngeoffray, 2013-12-05 16:32:23]

LGTM

https://codereview.chromium.org/102473004/diff/20001/sdk/lib/_internal/lib/is...
File sdk/lib/_internal/lib/isolate_helper.dart (right):

https://codereview.chromium.org/102473004/diff/20001/sdk/lib/_internal/lib/is...
sdk/lib/_internal/lib/isolate_helper.dart:240: isolateStatics =
JS_CREATE_ISOLATE();
Mark all the fields final and put their initialization code at their declaration
site?

[floitsch, 2013-12-05 17:08:35]

https://codereview.chromium.org/102473004/diff/20001/sdk/lib/_internal/lib/is...
File sdk/lib/_internal/lib/isolate_helper.dart (right):

https://codereview.chromium.org/102473004/diff/20001/sdk/lib/_internal/lib/is...
sdk/lib/_internal/lib/isolate_helper.dart:240: isolateStatics =
JS_CREATE_ISOLATE();
On 2013/12/05 16:32:23, ngeoffray wrote:
> Mark all the fields final and put their initialization code at their
declaration
> site?

:)
Had already started it to move the initializations, but then reverted that part.
Good point for making these fields final.

done.

[Lasse Reichstein Nielsen, 2013-12-06 08:00:03]

LGTM.
Is weak ports something we would want to expose to users?

[floitsch, 2013-12-06 09:32:07]

Committed patchset #3 manually as r30938 (presubmit successful).