Ok maybe it was 31:
static void ADIOI_W_Exchange_data(ADIO_File fd, void *buf, char *write_buf,
ADIOI_Flatlist_node *flat_buf, ADIO_Offset
*offset_list, int *len_list, int *send_size,
int *recv_size, ADIO_Offset off, int size,
int *count, int *start_pos, int *partial_recv,
int *sent_to_proc, int nprocs,
int myrank, int
buftype_is_contig, int contig_access_count,
ADIO_Offset min_st_offset, ADIO_Offset fd_size,
ADIO_Offset *fd_start, ADIO_Offset *fd_end,
ADIOI_Access *others_req,
int *send_buf_idx, int *curr_to_proc,
int *done_to_proc, int *hole, int iter,
MPI_Aint buftype_extent, int *buf_idx, int *error_code)
From the ROMIO implementation of MPI-IO :-). When I first saw this
function a few years ago my jaw dropped.... I'm still looking for
parts of it.
Dave
On 4/27/06, David Leimbach <[EMAIL PROTECTED]> wrote:
I've actually seen worse :) I saw a function in a certain library
with 36 parameters before.
On 4/27/06, Ronald G Minnich <[email protected]> wrote:
>
> this is from the openib mailing list :-)
>
> ron
> ===
> 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.
>
>
>
>
>
