db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kim Haase <Camilla.Ha...@Sun.COM>
Subject Re: Parameters vs Arguments in Derby Procedures
Date Wed, 18 Apr 2007 20:16:11 GMT
Yup, Jean's citation confirms my understanding (from many years of 
documenting programming languages) and yours, Laura. If you have an 
opportunity to correct the wording in topics that use the terms 
incorrectly, please take it! (And you're right, "parameters for" is better.)


Jean T. Anderson wrote:
> Laura Stewart wrote:
>> The Derby documentation needs to be accurate with regard to it's use
>> of the terms "parameter" and "argument". So I want to be certain that
>> I have an accurate understanding of the difference between parameters
>> and arguments.
> Hi, Laura,
> I confess to being someone who often uses the two interchangeably. This
> link ratifies your understanding (an argument is the value):
> http://en.wikipedia.org/wiki/Parameter_(computer_science)
>  -jean
>> It is my understanding that the syntax (or declaration) of the
>> procedure defines the parameters.  And an argument represents the
>> value you supply to a parameter when you call the procedure. There are
>> IN, OUT, and INOUT arguments.
>> For example, in the Derby IMPORT procedure
>> SYSCS_UTIL.SYSCS_IMPORT_TABLE (schemaName, tableName, fileName,
>> columnDelimiter, characterDelimiter, codeset, replace)
>> These are the parameter names.  Yes?  And when you supply the values,
>> those values are arguments. Yes?  So should the topic "Arguments to
>> the import procedures" which describes the schemaName, tableName, etc
>> be called "Arguments to ..." or "Parameters to.." ???
>> In my mind, it should be called "Parameters to the import procedures"
>> well actually "Parameters for the import procedures" bur that is a
>> separate issue :-)
>> Please help me have a clear understanding of  the terms "parameter"
>> and "argument".  Thanks!

View raw message