I'll take a look at the results of my Windows build. It should be
relatively easy to see if they are built at all. Built but not used is a
bit harder, and may take some experiments.
On 2/29/2016 11:02 AM, Dennis E. Hamilton wrote:
Patricia,
Take a look at main/sal/inc/osl/profile.h
Methinks that the code identified in
<https://bz.apache.org/ooo/show_bug.cgi?id=126669> might not be built
for current releases on Windows or Linux. You'll see that there are
filename suffixes such as .rc and .ini used. I doubt that has
anything to do with handling profiles now.
Is there a way we can check that the code is not built and/or and
these profile functions are not used?
I don't know about builds for OS/2 and other downstream builds that
we don't make ourselves.
And if the 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/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:
<https://bz.apache.org/ooo/show_bug.cgi?id=126669>.
Looks interesting. I am familiar with pthread and memory
management issues, so it may be a good area for me to work on.
Patricia
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
