[#4766] Wiki — "Glen Stampoultzis" <trinexus@...>

21 messages 2000/09/04
[#4768] RE: Wiki — "NAKAMURA, Hiroshi" <nahi@...> 2000/09/04

Hi, Glen,

[#4783] Re: Wiki — Masatoshi SEKI <m_seki@...> 2000/09/04

[#4785] Re: Wiki — "NAKAMURA, Hiroshi" <nakahiro@...> 2000/09/05

Howdy,

[#4883] Re-binding a block — Dave Thomas <Dave@...>

16 messages 2000/09/12

[#4930] Perl 6 rumblings -- RFC 225 (v1) Data: Superpositions — Conrad Schneiker <schneik@...>

Hi,

11 messages 2000/09/15

[#4936] Ruby Book Eng. translation editor's questions — Jon Babcock <jon@...>

20 messages 2000/09/16

[#5045] Proposal: Add constants to Math — Robert Feldt <feldt@...>

15 messages 2000/09/21

[#5077] Crazy idea? infix method calls — hal9000@...

This is a generalization of the "in" operator idea which I

17 messages 2000/09/22

[#5157] Compile Problem with 1.6.1 — Scott Billings <aerogems@...>

When I try to compile Ruby 1.6.1, I get the following error:

15 messages 2000/09/27

[ruby-talk:4996] Re: Ruby Book Ch 2 English -- arguments /parameters/options?

From: schneik@...
Date: 2000-09-18 19:13:12 UTC
List: ruby-talk #4996


Jon Babcock wrote:

> Should the explanation read, "Output the parameters sequentially." or
> "Output the arguments sequentially."  Or does it matter?

Some apparently common usage from the Oracle at Google:

http://www.cygnus.com/misc/wp/dec96pub/over.html

When  an  overloaded function name is used in a call, which overloaded
function declaration is being referenced is  determined  by  comparing
the  types  of the arguments at the point of use with the types of the
parameters in the overloaded declarations  that  are  visible  at  the
point of use.

http://msdn.microsoft.com/library/welcome/dsmsdn/deep07062000.htm

When evaluating the relative closeness of a candidate overload, your
compiler converts the caller's argument and return types to the
candidate's parameter and return types.

Conrad Schneiker
(This note is unofficial and subject to improvement without notice.)



In This Thread

Prev Next