<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">FYI, I’m changing the Fortran stub generator to read a file for these types, so it won’t be necessary to change the code in the stub generator. Still clunky but one step less so.<div><br></div><div>Bill</div><div><br></div><div><div><div>On Nov 28, 2014, at 6:43 AM, Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Every time we add a type to PETSc, we have to tell the Fortran stub generator about it. This is a clunky part of the</div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">design, but there is not enough momentum to change it.<span class="Apple-converted-space"> </span></div></blockquote></div><br></div></body></html>