るりまサーチ

最速Rubyリファレンスマニュアル検索!
39件ヒット [1-39件を表示] (0.045秒)

別のキーワード

  1. _builtin call
  2. call
  3. method call
  4. continuation call
  5. tracer display_c_call

ライブラリ

クラス

検索結果

XMLRPC::Client#call2(method, *args) (18108.0)

The difference between this method and XMLRPC::Client#call is, that this method do ((*not*)) raise a XMLRPC::FaultException exception. The method returns an array of two values. The first value indicates if the second value is a return-value (true) or an object of type XMLRPC::FaultException. Both are explained in XMLRPC::Client#call.

...tion exception.
The method returns an array of two values. The first value indicates if
the second value is a return-value (true) or an object of type
XMLRPC::FaultException.
Both are explained in XMLRPC::Client#call.

Simple to remember: The "2" in "call2" denotes the number of values it returns....

XMLRPC::Client#multicall2(*methods) (6117.0)

Same as XMLRPC::Client#multicall, but returns like XMLRPC::Client#call2 two parameters instead of raising an XMLRPC::FaultException.

...Same as XMLRPC::Client#multicall, but returns like XMLRPC::Client#call2 two parameters
instead of raising an XMLRPC::FaultException....

XMLRPC::Client#call2_async(...) (6102.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#multicall2_async(...) (6102.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#call_async(...) (3002.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

絞り込み条件を変える

XMLRPC::Client#multicall_async(...) (3002.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#proxy2_async(...) (3002.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#proxy_async(...) (3002.0)

In contrast to corresponding methods without "_async", these can be called concurrently and use for each request a new connection, where the non-asynchronous counterparts use connection-alive (one connection for all requests) if possible.

In contrast to corresponding methods without "_async", these can be
called concurrently and use for each request a new connection, where the
non-asynchronous counterparts use connection-alive (one connection for all requests)
if possible.

Note, that you have to use Threads to call these methods co...

XMLRPC::Client#proxy2(prefix, *args) (17.0)

Almost the same like XMLRPC::Client#proxy only that a call on the returned XMLRPC::Client::Proxy object behaves like XMLRPC::Client#call2, i.e. a call on that object will return two parameters.

...Almost the same like XMLRPC::Client#proxy only that a call on the returned
XMLRPC::Client::Proxy object behaves like XMLRPC::Client#call2, i.e.
a call on that object will return two parameters....

BasicObject#instance_eval {|obj| ... } -> object (13.0)

オブジェクトのコンテキストで文字列 expr またはオブジェクト自身をブロックパラメータとするブロックを 評価してその結果を返します。

...# file.rb:999: unknown (RuntimeError)

例:

class Bar < BasicObject
def call1
instance_eval("::ENV.class")
end
def call2
instance_eval("ENV.class")
end
end

bar = Bar.new
bar.call1 # => Object
bar.call2 # raise NameError

@see Module#module_eval, Kernel.#eval...

絞り込み条件を変える

BasicObject#instance_eval(expr, filename = "(eval)", lineno = 1) -> object (13.0)

オブジェクトのコンテキストで文字列 expr またはオブジェクト自身をブロックパラメータとするブロックを 評価してその結果を返します。

...# file.rb:999: unknown (RuntimeError)

例:

class Bar < BasicObject
def call1
instance_eval("::ENV.class")
end
def call2
instance_eval("ENV.class")
end
end

bar = Bar.new
bar.call1 # => Object
bar.call2 # raise NameError

@see Module#module_eval, Kernel.#eval...