[lldb-dev] Frame documentation
badlogicgames at gmail.com
Sun Nov 30 11:00:19 PST 2014
Same 'issue' here, altough i found most things to be intuitive by checking
the core classes used by the public API. The only thing that i think needs
more attention is the event mechanism, how to use it, what not to do etc.
I'd volunteer to submit doxygen patches for the public API if this becomes
a coordinated effort.
On Nov 30, 2014 7:48 PM, "Zachary Turner" <zturner at google.com> wrote:
> I've been running into similar issues as you regarding documentation. What
> ive been doing is asking here -- as you're doing -- and then submitting
> patches to improve comments. That said, I generally prefer in-code comments
> over external documentation because external documentation is almost
> guaranteed to get out of date sooner or later
> On Sun, Nov 30, 2014 at 4:36 AM Jose H <jose.francisco.hevia at gmail.com>
>> Just being curious(and not loving the fact of using something without
>> understanding it, what the last argument of frame.GetVariable does?.
>> It says:
>> DynamicValueType use_dynamic
>> In the c++ documentation it says I could use those values:
>> eDynamicCanRunTarget, eNoDynamicValues, eDynamicCanRunTarget,
>> What dynamic value type means?. It means c++ auto or something like a
>> template value?.
>> How can someone help improve the lldb documentation, so the same
>> questions do not need to be answered again. I mean how I could help
>> complete the documentation with the same answers you have provided but
>> adding some visuals?
>> This area needs diagrams and pictures to make it easier to get the big
>> picture fast.
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev