The return value of a successful call to kcmp() is simply the result of arithmetic comparison of kernel pointers(when the kernel compares resources, it uses their memory addresses).
As a result, if there is not sufficient entropy in the entropy pool, the returned values are theoretically vulnerable to a cryptographic attack on the algorithms used by the driver.
If a shell could not be executed in the child process, then the return value is as though the child shell terminated by calling_exit(2) with the status 127.
The"result" of Main. main() is insignificant- probably a unit return value, but I haven't checked- and it doesn't get returned until the application finally exits.
In the last two cases, the return value is a"wait status" that can be examined using the macros described in waitpid(2).(i.e., WIFEXITED() WEXITSTATUS() and so on).
に格納できない場合、領域エラー(domainerror)が発生し、返り値は不定となる。
then a domain error occurs, and the return value is unspecified.
The value returned by this property may not be the same as the one specified when calling the constructor as it may be changed to match internal requirements.
返り値は常にElementです。
The return value is always an integer.
返り値は無視されます。
The return value is ignored.
返り値は実装によって異なります。
The return value will vary based on the implementation.
返り値はユーザの入力次第です。
The return value depends on the user's response.
返り値はデータベースのファイルディスクリプタである。
The return value will be the file descriptor of the database.
English
中文
عربى
Български
বাংলা
Český
Dansk
Deutsch
Ελληνικά
Español
Suomi
Français
עִברִית
हिंदी
Hrvatski
Magyar
Bahasa indonesia
Italiano
Қазақ
한국어
മലയാളം
मराठी
Bahasa malay
Nederlands
Norsk
Polski
Português
Română
Русский
Slovenský
Slovenski
Српски
Svenska
தமிழ்
తెలుగు
ไทย
Tagalog
Turkce
Українська
اردو
Tiếng việt