[petsc-dev] Use of '//' comments in C source

[Jed Brown]

Furthermore, if the C++ source used a different suffix, then macros like
SETERRXX could be used from "normal" builds of PETSc. PETSc is the only
library I know where you are semi-expected to build the library differently
depending on your calling language.
On Sep 22, 2011 6:40 PM, "Jed Brown" <jedbrown at mcs.anl.gov> wrote:
> We should fix that.
> On Sep 22, 2011 6:37 PM, "Matthew Knepley" <knepley at gmail.com> wrote:
>> On Thu, Sep 22, 2011 at 9:27 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>>
>>> On Thu, Sep 22, 2011 at 18:16, Matthew Knepley <knepley at gmail.com>
wrote:
>>>
>>>> I originally did this and Barry vetoed using another suffix.
>>>
>>>
>>> But not *.c. I don't care what you use, dammit, just be consistent and
>>> don't use *.c for C++-only code.
>>>
>>
>> You miss my point. I used .cxx (see early Sieve examples), and anything
> but
>> .c was out. There is other
>> C++ source with .c.
>>
>> Matt
>>
>> --
>> What most experimenters take for granted before they begin their
> experiments
>> is infinitely more interesting than any results to which their
experiments
>> lead.
>> -- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110922/b4414fb5/attachment.html>