Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I5262899171029772f53dccc9aea666c4b83aef36
|
|
Change-Id: I08959c0de113264aaa7b1ca8c4f3124b2177d30f
|
|
Change-Id: If9faa49b3d3fc36f36db4a7cc6ab82f8af54935a
|
|
so that they locate where their classes appear if needed,
otherwise removed
Change-Id: I457542ec4c31f9a4b56a562f588b7c190c18776c
|
|
Change-Id: I6c145e984c885c7e06caa1c27bfb354ea49ad9ce
|
|
There are still some pch headers in use. Simply:
find . -name *_pch*
Change-Id: Idafcd4f1451877ad9b08c8bbea526266d7414553
|
|
Change-Id: I043e226a1cec527c51cbd91075634d5c9ca371d8
|
|
Change-Id: I994119c0520658775d07f776237d31a03f53ab52
|
|
It only included <tools/solar.h>, so include that directly instead.
Change-Id: Ic5db474c16ca33dcdcaabb5b5f00535b4b27dc8f
|
|
And use it both in the core interpreter and the configuration UI.
Change-Id: Ia2a16fcb53025840d906864b564255cd3c53e8e9
|
|
Change-Id: Ic9ba214e5bbee64287934437fcdb63117a1146f6
|
|
Change-Id: I082ea20d02bf37d515fc33d627281696fc48fcb6
|
|
|
|
|
|
SAL_UNUSED_PARAMETER (expanding to __attribute__ ((unused)) for GCC)
is used to annotate legitimately unused parameters, so that static
analysis tools can tell legitimately unused parameters from truly
unnecessary ones. To that end, some patches for external modules
are also added, that are only applied when compiling with GCC and
add necessary __attribute__ ((unused)) in headers.
|
|
|
|
|
|
|
|
Hello lo-devs,
this patch series removes a lot of unnecessary includes for the various
tools header. The patches without suffix should be applied to the core
repository, the .binfilter.patch suffix should be applied to the
binfilter repository. I've tested the build with the configuration
--enable-binfilter --enable-dbgutil --enable-debug, is this sufficient
or did I miss another important configuration, that enables some
conditional compiled code? I've only build this on linux-x86_64, but the
patch also touches some of the mac specific code like
fpicker/source/aqua/SalAquaFilePicker.mm so it would be maybe a good
idea to test this patch.
regards Marcel Metz
|
|
For now, only COL and ROW are supported. More on the way. Note that
we can't support all the information types that we do for internal
references.
|
|
|
|
from <regina>, slightly reworked
# HG changeset patch
# User Eike Rathke [er] <eike.rathke@oracle.com>
# Date 1291394833 -3600
# Node ID ff05fcb4fe392f8c336466982a25fdfda207515a
# Parent 4ca136c3f3c8eb330664884c2ff79e2027d8e4eb
|
|
database functions QueryParam
# HG changeset patch
# User Niklas Nebel <nn@openoffice.org>
# Date 1290620646 -3600
# Node ID 96608d83032e60946c80e0a5185a55843b74eb6f
# Parent 427eca1ec1adf81ed3016bde2ef2b010c9fd9ed1
|
|
Or else the pTokenMatrixMap would never yield any match. This was
the only reason behind the poor performance of resolving jump matrix
as exhibited in the aforementioned bug...
|
|
|
|
|
|
They are only referenced in interpr1.cxx.
|
|
Because I'll be modifying this struct in the next few days...
|
|
Implements BITAND, BITOR, BITXOR, BITLSHIFT and BITRSHIFT as specified by
OASIS OpenDocument Format 1.2 OpenFormula / ODFF.
Changes made by the committer:
* Original submission added the new functions to the Logical group, that group
has only functions though that return a logical value 1/0/true/false. ODFF
groups them under "Bit operation functions" that currently is not available
in Calc. Added the functions to the Mathematical group instead.
* Changed descriptions of functions in the Function Wizard.
* One sal_uInt64 constant instead of several identical literal 281474976710655
values.
* Replaced 'or' operators with ||
* Don't push two return values, if PushIllegalArgument() was used don't use
PushDouble() thereafter.
* Treat double values with ::rtl::math::approxFloor() to obtain integer
values.
* For BITLSHIFT and BITRSHIFT implemented a different algorithm following the
ODFF specification that allows larger shift values.
* Use our block braces style, respectively don't use block braces for one-line
if-statements.
* Fixed indentation levels.
* Adapted RTL_LOGFILE_CONTEXT_AUTHOR to say "pechlaner". Credit to whom credit
is due ;-)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I'm deleting the header since it's no longer used.
|
|
That deliberately mis-spelled header name always bothered me. Now
fixed once and for all.
For the record, the original file name was inspired by the 8-character
rule that some of the old compilers that the Hamburg guys had to use,
years and years ago.
|
|
|
|
|
|
|
|
Turns out that the token array's recalc mode is set to "recalc always"
when it contains a volatile token during compilation. We can re-use
that to mark the token array volatile before the interpretation starts.
The end result is the same, with better performance since we can avoid
re-scanning of the token array.
|
|
When a volatile token is inside a conditional function (such as IF),
*and* the evaluation of that conditional skips the volatile token
it would incorrectly mark the cell non-volatile. The solution is
to scan through all tokens in the token array in the beginning of
the calculation and mark the cell volatile if one is found.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|