Procedure call template missing brackets

Ralph Weber roweber at ieee.org
Fri Apr 12 05:33:47 PDT 2013


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1304120_f.htm">HTML-formatted message</a>

George,
As requested, a proposal has been posted to the CAP agenda.
http://www.t10.org/cgi-bin/ac.pl?t=d&f=13-117r0.pdf
All the best,
.Ralph
On 4/10/2013 3:11 PM, Penokie, George wrote:
>
> Ralph,
>
> Adding the [] maybe not 100% correct but it is right now it is 100% in 
> conflict with normative requirements so until someone comes up with a 
> better solution the []s stay.
>
> Bye for now,
>
> George Penokie
>
> LSI Corporation
>
> 3033 41 St NW
>
> Rochester , MN 55901
>
> 507-328-9017
>
> george.penokie at lsi.com
>
> *From:*Ralph Weber [mailto:Ralph.Weber at wdc.com]
> *Sent:* Wednesday, April 10, 2013 2:56 PM
> *To:* Penokie, George; Elliott, Robert (Server Storage); Ie Wei Njoo 
> (IeWei.Njoo at pmcs.com); Curtis Stevens
> *Cc:* Stephen Finch; bill.martin at ssi.samsung.com; T10 Reflector
> *Subject:* RE: Procedure call template missing brackets
>
> I have two problems with this.
>
> First, it smacks of an attempt to employ a usage notation for 
> interfaces (i.e., []) as a way of placing requirements the way T10 
> standards are written.
>
> Second, it implies that the following notation would also be allowed 
> [input-5, input-6] (i.e., the change leaves the reader with no 
> alternative other than believing that groups of arguments can be 
> marked optional), which is rather a stretch when compared to current 
> usage.
>
> A text note to the effect that procedure calls are allowed to omit 
> output arguments if none are defined seems like a more honest (and 
> less dubious) approach to the problem.
>
> All the best,
>
> .Ralph
>
> ------------------------------------------------------------------------
>
> *From:*Penokie, George [George.Penokie at lsi.com]
> *Sent:* Wednesday, April 10, 2013 1:39 PM
> *To:* Elliott, Robert (Server Storage); Ie Wei Njoo 
> (IeWei.Njoo at pmcs.com); Curtis Stevens
> *Cc:* Stephen Finch; Ralph Weber; bill.martin at ssi.samsung.com; T10 
> Reflector
> *Subject:* RE: Procedure call template missing brackets
>
> Rob,
>
> I agree that the OUT need []s, however, all procedures currently 
> defined have the IN. So I will add the [] around the OUT in SAM, SPL, 
> and the style guide as an editorial change.
>
> Bye for now,
>
> George Penokie
>
> LSI Corporation
>
> 3033 41 St NW
>
> Rochester , MN 55901
>
> 507-328-9017
>
> george.penokie at lsi.com
>
> *From:*Elliott, Robert (Server Storage) [mailto:Elliott at hp.com]
> *Sent:* Wednesday, March 13, 2013 8:22 PM
> *To:* Penokie, George; Ie Wei Njoo (IeWei.Njoo at pmcs.com); 
> curtis.stevens at wdc.com
> *Cc:* Stephen Finch (WD)
> *Subject:* Procedure call template missing brackets
>
> As Steve Finch found:
>
> [Result =] Procedure Name (IN ( [input-1] [,input-2] ...]), OUT ( 
> [output-1] [,output-2] ... ))
>
> s/b
>
> [Result =] Procedure Name ([IN ([input-1][,input-2] ...]),][OUT 
> ([output-1][,output-2] ... )])
>
> to avoid requiring blank OUT() or IN() arguments, which is not done in 
> SAM-5 or any other standard.
>
> Example in SAM-5:
>
> Send SCSI Command (IN ( I_T_L_Q Nexus, CDB, Task Attribute, [Data-In 
> Buffer Size],
>
> [Data-Out Buffer], [Data-Out Buffer Size], [CRN], [Command Priority], 
> [First
>
> Burst Enabled] ))
>



More information about the T10 mailing list