[1]: A generally useful module (e.g. one exhibiting an OS API) should have a short, reasonably clear, but potentially unique name. Note that all module names share the same name space, so be careful when naming your module to avoid potential conflicts.

[2]: Static linking is currently restricted to the standard modules of m. If you want to add your own native modules to a statically linked m application, you must add them as DLL.

[3]: In fact, m for Symbian is completely developed and maintained under Linux.

[4]: m user permissions are unrelated to the Symbian 3rd/5th Edition security model which attempts to address this issue to some extent at the OS level with a combination of capabilities and signed installers.

[5]: The required library alarmshared.lib is missing from most S60 SDKs, but you can safely copy the file from e.g. the UIQ SDK in this case.

[6]: There are tools to modify the capabilities of the executables in a SIS file and re-sign it, gaining complete flexibility over capabilities (within the limits of platform security, of course). You should however assume that other m installations will run with either of the capabilities listed here.