diff options
author | Björn Gustavsson <[email protected]> | 2016-01-27 14:52:15 +0100 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2016-01-27 16:33:24 +0100 |
commit | b42d79a563993bacafcd3e4be24f324406e65c26 (patch) | |
tree | 2304f52d10fd9095751b4d683884d2d8d754f41b /erts/test/upgrade_SUITE_data | |
parent | db61a493f72cc13f3e9b709b8e86da7e3d246f2b (diff) | |
download | otp-b42d79a563993bacafcd3e4be24f324406e65c26.tar.gz otp-b42d79a563993bacafcd3e4be24f324406e65c26.tar.bz2 otp-b42d79a563993bacafcd3e4be24f324406e65c26.zip |
Simplify starting of code server
There is unnecessary knowledge about the -nostick option
in the 'kernel' module. -nostick can be handled entirely
in the 'code' module.
There is no need to have both code:start_link/0 and
code:start_link/1. code:start_link/0 is sufficient.
Also get rid of error handling for things that cannot happen:
The 'init' module has made sure that init:get_argument(root)
can't fail, so there is no need for any error-reporting code.
(See e1dc0aa4.)
We also don't need to test the return value from
code_server:start_link/1, because it will always return {ok,Pid}
(or crash).
Diffstat (limited to 'erts/test/upgrade_SUITE_data')
0 files changed, 0 insertions, 0 deletions