From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e1162e60604272339q5cb30641tfb67affedbee50ce@mail.gmail.com> Date: Thu, 27 Apr 2006 23:39:19 -0700 From: "David Leimbach" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] too good to pass up In-Reply-To: <44514985.8060403@lanl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <44514985.8060403@lanl.gov> Topicbox-Message-UUID: 49a1cc32-ead1-11e9-9d60-3106f5b1d025 I've actually seen worse :) I saw a function in a certain library with 36 parameters before. On 4/27/06, Ronald G Minnich wrote: > > this is from the openib mailing list :-) > > ron > =3D=3D=3D > On Thu, 27 April 2006 12:49:36 +0200, Heiko J Schick wrote: > > >> +u64 hipz_h_alloc_resource_qp(const struct ipz_adapter_handle > >> adapter_handle, > >> + struct ehca_pfqp *pfqp, > >> + const u8 servicetype, > >> + const u8 daqp_ctrl, > >> + const u8 signalingtype, > >> + const u8 ud_av_l_key_ctl, > >> + const struct ipz_cq_handle send_cq_handle, > >> + const struct ipz_cq_handle receive_cq_handle= , > >> + const struct ipz_eq_handle async_eq_handle, > >> + const u32 qp_token, > >> + const struct ipz_pd pd, > >> + const u16 max_nr_send_wqes, > >> + const u16 max_nr_receive_wqes, > >> + const u8 max_nr_send_sges, > >> + const u8 max_nr_receive_sges, > >> + const u32 ud_av_l_key, > >> + struct ipz_qp_handle *qp_handle, > >> + u32 * qp_nr, > >> + u16 * act_nr_send_wqes, > >> + u16 * act_nr_receive_wqes, > >> + u8 * act_nr_send_sges, > >> + u8 * act_nr_receive_sges, > >> + u32 * nr_sq_pages, > >> + u32 * nr_rq_pages, > >> + struct h_galpas *h_galpas); > > > 25 parameters? If you tell me which drugs were involved in this code, > I know what to stay away from. Might be the current record for any > code ever proposed for inclusion. > > > > >