On 11/09/2017 05:28 PM, Alexander Thurgood wrote:
> Errm, seriously, not really, other than perhaps just focussing on one area of
> the code.
:(
> thereby making it difficult to have increasing in-depth knowledge and
> insights. That knowledge kind of tends to be assumed.
Not to mention that
On 11/09/2017 12:28 PM, Alexander Thurgood wrote:
> Le 09/11/2017 à 16:30, jonathon a écrit :
>
> Any pointers on how to minimise the pain of reading the code?
>
> Aspirin ;-)
May the source be with you. ;-)
--
To unsubscribe e-mail to: users+unsubscr...@global.libreoffice.org
Problems?
Le 09/11/2017 à 16:30, jonathon a écrit :
Any pointers on how to minimise the pain of reading the code?
Aspirin ;-)
Errm, seriously, not really, other than perhaps just focussing on one
area of the code. I tend to mostly focus on the database stuff, and have
recently started looking at memory
On 11/09/2017 09:04 AM, Alexander Thurgood wrote:
> As a non-developer trying to read the code for bug hunting, it has given me
> migraines on many an occasion.
Any pointers on how to minimise the pain of reading the code?
jonathon
--
To unsubscribe e-mail to:
On 09/11/17 09:04, Alexander Thurgood wrote:
Le 08/11/2017 à 10:52, Mike Scott a écrit :
Hi Mike,
Having established it would build and run (with the same video problem,
incidentally), I finally looked at the sources. Now I begin to see why
changes take so long not a comment in sight for
Le 08/11/2017 à 10:52, Mike Scott a écrit :
Hi Mike,
> Having established it would build and run (with the same video problem,
> incidentally), I finally looked at the sources. Now I begin to see why
> changes take so long not a comment in sight for one thing, and a
> spider's web of
