Barry Smith <[email protected]> writes: > Another alternative is to have inside the DMKSP a pointer to the > "active" KSP (make it a void pointer so that there is no circular > dependencies)
DMKSP is in the KSP package, so there is no problem with circular dependencies. > and only use the DMKSP functions if the current KSP is the "active" > KSP. Of course now we still need to set this pointer to the > appropriate KSP (the first one set with KSPSetDM()? by default). Is > there any advantage to this? (Same for snes also). I think it's cosmetic except that a DM field is more permissive in that it could have a different DM. I can't think of a reason to want that.
signature.asc
Description: PGP signature
