Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

In the short term, incremental and iterative can go well, but in the long term it only makes the bit rot worse. I have had bad experiences both ways, so neither course guarantees success. Thread synchronization is a particularly dangerous area for not having a known design, because it can lead to

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

e: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > On 3/4/2016 9:39 AM, Dennis E. Hamilton wrote: > > Patricia, > > > > Based on Damjan's finding that profile files are read by the > > application and that some are created during setup, w

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/4/2016 9:39 AM, Dennis E. Hamilton wrote: Patricia, Based on Damjan's finding that profile files are read by the application and that some are created during setup, with others copied in from the setup, it is settled that the code is used in current distributions and is also available to ex

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

Damjan, A question below. > -Original Message- > From: Damjan Jovanovic [mailto:dam...@apache.org] > Sent: Friday, March 4, 2016 04:41 > To: Apache OO > Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > On Fri, Mar 4, 2016 at 11:

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

ies deserve our attention. - Dennis > -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Friday, March 4, 2016 05:23 > To: dev@openoffice.apache.org > Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > > &

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/3/2016 5:00 PM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] ... I am curious about whether it started out with pthread_mutex uses and lost them along the way, or whether that difference between unx and w32 is primordial. [orcmid] You

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/4/2016 4:40 AM, Damjan Jovanovic wrote: On Fri, Mar 4, 2016 at 11:59 AM, Patricia Shanahan wrote: On 3/4/2016 12:54 AM, Damjan Jovanovic wrote: ELF binaries (Linux, *BSD) fundamentally use one of the worst ideas of all time: symbols are process scoped (unlike on Windows and MacOS where

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On Fri, Mar 4, 2016 at 11:59 AM, Patricia Shanahan wrote: > On 3/4/2016 12:54 AM, Damjan Jovanovic wrote: >> >> ELF binaries (Linux, *BSD) fundamentally use one of the worst ideas of >> all time: symbols are process scoped (unlike on Windows and MacOS >> where they're library scoped), meaning that

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/4/2016 12:54 AM, Damjan Jovanovic wrote: ELF binaries (Linux, *BSD) fundamentally use one of the worst ideas of all time: symbols are process scoped (unlike on Windows and MacOS where they're library scoped), meaning that symbols with the same name can clash even if in different libraries lo

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/3/2016 5:00 PM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Thursday, March 3, 2016 14:38 To: dev@openoffice.apache.org Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning curve) I am seriously considering

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

ffice.apache.org >>> Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning >>> curve) >>> >>> I am seriously considering starting a project to eliminate profile.c >>> etc. and seeing what, if anything, breaks. >>> >>> Befo

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

ursday, March 3, 2016 17:43 > To: dev@openoffice.apache.org > Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > On 3/3/2016 5:00 PM, Dennis E. Hamilton wrote: > >> -Original Message- > >> From: Patricia Shanahan [mailto:p...@acm

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/3/2016 5:00 PM, Dennis E. Hamilton wrote: -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Thursday, March 3, 2016 14:38 To: dev@openoffice.apache.org Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning curve) I am seriously considering starting

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Thursday, March 3, 2016 14:38 > To: dev@openoffice.apache.org > Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > I am seriously considering starting a projec

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

I am seriously considering starting a project to eliminate profile.c etc. and seeing what, if anything, breaks. Before I do that, I have a question about whether it could be accessed through any of OpenOffice's extension or plugin facilities? Even if it can, 14 years seems quite long enough fo

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

ennis E. Hamilton [mailto:dennis.hamil...@acm.org] > Sent: Wednesday, March 2, 2016 11:42 > To: dev@openoffice.apache.org > Subject: RE: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > > > > -Original Message- > > From: Patricia Shanahan

RE: Profile.c bugs (was RE: Some thoughts on the learning curve)

> -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Wednesday, March 2, 2016 10:25 > To: dev@openoffice.apache.org > Subject: Re: Profile.c bugs (was RE: Some thoughts on the learning > curve) > > Dennis, > > The build output from

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

code is really obsolete, we should prune it from trunk and source releases. - Dennis -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Saturday, February 20, 2016 20:57 To: dev@openoffice.apache.org Subject: Re: Some thoughts on the learning curve On 2/20/

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 3/1/2016 6:31 AM, Pedro Giffuni wrote: Hi Patricia; Good analysis, thank you! I think the operation is invalid. We can just comment out the code. FWIW, I looked at the SUN history to see if I could guess what the author pretended: https://bitbucket.org/mst/ooo340/annotate/8b564af029aa60259

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

Hi Patricia; Good analysis, thank you! I think the operation is invalid. We can just comment out the code. FWIW, I looked at the SUN history to see if I could guess what the author pretended: https://bitbucket.org/mst/ooo340/annotate/8b564af029aa60259c0d133d7dc37468ef56e4b5/sal/osl/unx/profi

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

On 2/29/2016 7:41 PM, Pedro Giffuni wrote: Hello; FWIW, I have looked at i126669 and Coverity confirms there is a bug there. CID 440168 (#1 of 1): Dereference after null check (FORWARD_NULL)9. var_deref_model: Passing null pointer "&pProfile->m_AccessLock" to function "pthread_mutex_unlock(pthr

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

Hello; FWIW, I have looked at i126669 and Coverity confirms there is a bug there. CID 440168 (#1 of 1): Dereference after null check (FORWARD_NULL)9. var_deref_model: Passing null pointer "&pProfile->m_AccessLock" to function "pthread_mutex_unlock(pthread_mutex_t *)", which dereferences it.

Re: Profile.c bugs (was RE: Some thoughts on the learning curve)

is -Original Message- From: Patricia Shanahan [mailto:p...@acm.org] Sent: Saturday, February 20, 2016 20:57 To: dev@openoffice.apache.org Subject: Re: Some thoughts on the learning curve On 2/20/2016 8:39 PM, Dennis E. Hamilton wrote: I sympathize with Pedro's observation. Meanwhile,

Profile.c bugs (was RE: Some thoughts on the learning curve)

e, we should prune it from trunk and source releases. - Dennis > -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Saturday, February 20, 2016 20:57 > To: dev@openoffice.apache.org > Subject: Re: Some thoughts on the learning curve > > >

Re: Some thoughts on the learning curve

On 2/20/2016 8:39 PM, Dennis E. Hamilton wrote: I sympathize with Pedro's observation. Meanwhile, although I am not an expert, I could stand to buddy up on the following profile-related situation: . Looks interesting. I am familiar with pthre

RE: Some thoughts on the learning curve

hat there can be binding votes for. It doesn't matter what we fix if we can't ship it. - Dennis > -Original Message- > From: Patricia Shanahan [mailto:p...@acm.org] > Sent: Saturday, February 20, 2016 18:19 > To: dev@openoffice.apache.org > Subject: Some thoughts on t

Re: Some thoughts on the learning curve

Hi, I am one of the newcomers you speak about, I’m a college undergraduate trying to do something with AOO, and yes, I also find the learning curve quite steep. I started out gradually, and was focussing on implementing the bitwise functions in calc at the start. I must say here that Da

Re: Some thoughts on the learning curve

Hi Patricia; One disclaimer that I should make is that I am not actually an experienced OpenOffice developer. I only joined the project when it moved to the ASF and there were so many things to do that I basically managed to do a lot of stuff without having to learn the internals too much. Your a

Some thoughts on the learning curve

One of the biggest problems facing AOO is getting new developers up to speed. As I understand it, there is a small group of developers who do understand AOO, but do not have anywhere near enough time to do everything that needs doing. Meanwhile, you have newcomers with various levels of exper