> > none of the other have the space after the asterisk. Hmmm, in case > > the email messes up the exact spacing, the second is "left paren" > > "asterisk" "space" "Saved...". Is that right? > > > > xorg-server-1.8.2/Xext/panoramiXprocs.c: return > > (*SavedProcVector[X_PolyFillRectangle])(client); > > xorg-server-1.8.2/Xext/panoramiXprocs.c: result = (* > > SavedProcVector[X_PolyFillRectangle])(client);
Note that the email wordwrap cut it after the asterisk, not before the left paren as in the previous statement. There was a space there. > > > > Can I just patch that back together? > > Patch what together? > > The line result = (*SavedProcVector[X_PolyFillRectangle])(client); > assigns the returned value of a called function to result. > > SavedProcVector is an array of pointers to functions with a parameter > of a pointer to a structure called _Client which is defined in > include/dixstruct.h Yes, I got the semantics. It's not that different than other languages. It's just a detail of the syntax I have to ask about. There is a space between the asterisk and the "S" on one statement. Is that optional, or must they be contiguous, as they are in all the other statements? How does the space change the meaning, if at all? TIA -- Paul Rogers paulgrog...@fastmail.fm http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.fm - Email service worth paying for. Try it for free -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
