Re: void * pointer convert problem.



 
"tmp123" <tmp123@xxxxxxxxx> wrote in message news:1135970785.059294.45060@xxxxxxxxxxxxxxxxxxxxxxxxxxxx...
> >     317     void*       bPtr;
> >     325     bPtr = (proc_timing_bin_p)(&hPtr->ptBin[0]);
> >     329     bPtr = (exec_timing_bin_p)(&hPtr->etBin[0]);
> >     342     if(key < bPtr->key)
>
> Hi,
>
> a) If the field key has the same offset in both strutures (proc and
> exec), then you can use anyone:
>
> if (key < (proc_timing_bin_p *)bPtr->key ) ....
>
> b) If the offset is not the same, your request has no solution. The
> most near is:
>
> if (key < (hbt == PROC_TIMING_BIN)?(proc_timing_bin_p
> *)bPtr->key:(exec_timing_bin_p *)bPtr->key ) ...
>
> Kind regards.
>
 
Yeah! They have same offset, so I can choose the first solution.
 
 
Thanks,
Eric


Relevant Pages

  • Re: void * pointer convert problem.
    ... If the field key has the same offset in both strutures (proc and ... exec), ... If the offset is not the same, ...
    (comp.lang.c)
  • Re: SqlDataAdapter1.SelectCommand.CommandType= CommandType.StoredProcedure
    ... >> kann man beim EXEC PROC keine Parameter beifügen. ... > da das TDS Protokoll das intern unterscheiden kann. ... > nach der Ausführung ungültig werden. ...
    (microsoft.public.de.german.entwickler.dotnet.datenbank)
  • Re: using nexted procs
    ... So I have a cataloged proc 'FJS.PDSE.PROC' that looks like this: ... //IEFRDER DD DUMMY //SYSUOUT DD SYSOUT=* ... //FFND05 EXEC DLIBATCH,DLIPGM=FFND05,DLIPSB=FFUNDGO ... Our goal was that when testing we would execute the production proc and override the DD names to the names of test files. ...
    (bit.listserv.ibm-main)
  • typo error...
    ... First Proc should be p1 and not p3 ... > exec p1 ... >> Over night we take a copy of various live SQL databases onto another SQL ... >> I connect to the live databases using linked servers. ...
    (microsoft.public.sqlserver.programming)
  • Re: Strangeness in PROC-land
    ... //STEP1 EXEC PGM=IEFBR14 ... It complains about the second PEND because you can not nest PROCs inside ... instream data inside a PROC. ... But the JCL error is on the second PEND ...
    (bit.listserv.ibm-main)