[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 371916] execution tree xtree concept
From:       Ivo Raisr <bugzilla_noreply () kde ! org>
Date:       2016-11-03 23:24:27
Message-ID: bug-371916-17878-I84k63ehRQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=371916

Ivo Raisr <ivosh@ivosh.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |CONFIRMED

--- Comment #8 from Ivo Raisr <ivosh@ivosh.net> ---
Thank you, Philippe, for answering my questions.
I have an additional one and then some docs stuff below.


>> 4. Functions in this header file use a mixture of camelCase and
>> all_lower_case which is inconsistent and  disturbs reader's eyes. Can you do
>> something with it?

> Humph, that is a very valuable comment, but I am not sure what style
> to use.

Alright. But you can unify the function names so their names are consistent
among themselves. Consider this random selection:
VG_(newXT)()
VG_(xt_filter_maybe_below_main)()
VG_(xt_offset_main_or_below_main)()
VG_(init_XtAllocs)()
VG_(XtMemoryFull_init)()
VG_(XtMemoryFull_resizeInPlace)()
VG_(XtMemory_report)()
VG_(snapshotXT)()
VG_(subFromXT)()
VG_(n_ips_sel)()
VG_(XtPrint_callgrind)()
VG_(XtClose_massif)()

Sometimes the function name follows pattern: "XTthing_operation",
sometimes "operationXT" and sometimes something completely different.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]