summaryrefslogtreecommitdiff
path: root/tools
AgeCommit message (Collapse)AuthorFilesLines
2011-12-22Revert "callcatcher: Remove unused code"August Sodora6-0/+94
This reverts commit bbad7057b2bdb614a5e97a945039323efe39c4ee.
2011-12-22callcatcher: Remove unused codeAugust Sodora6-94/+0
2011-12-21I hate you poxy msvcCaolán McNamara2-2/+2
2011-12-21tweak for pre language-defect #77Caolán McNamara4-14/+14
2011-12-21disentangle Read/WriteByteString OUString variantsCaolán McNamara3-9/+10
The ones which use a definite 8-bit encoding read/write pascal-style strings with a 16bit length prefix. The ones which use a definite 16-bit encoding read/write pascal-style UTF-16 strings with a 32bit length prefix, i.e. not ByteStrings at all The "I dunno" ones might be UTF-16 strings or 8-bit strings, depending on the charset. Rename to ReadUniOrByteString like the other similar horrors to flag this misery
2011-12-21convert ReadByteString/WriteByteString from ByteString to OStringCaolán McNamara6-101/+169
Nobody ever used the return values anyway, so for reading just return the string and for writing the number of bytes written Doesn't need to be members, make standalone functions Rename to read_lenPrefixed_uInt8s_ToO[U]String and write_lenPrefixed_uInt8s_FromO[U]String, lengthy, but much less unambiguous, seeing as a lot of users of it don't seem to be aware that they read/write pascal-style length prefixed strings, which isn't surprising given the apparent simplicity of their original name. added a unit test
2011-12-21needs more work firstCaolán McNamara6-169/+101
This reverts commit 92f396733ebc518bcb7a9eae2dd3169d333b82b9.
2011-12-21bah, need to tweak for pre c++0xCaolán McNamara3-10/+9
This reverts commit d00fc0e293852cfc019ffaffa65bee327397677b.
2011-12-21disentangle Read/WriteByteString OUString variantsCaolán McNamara3-9/+10
The ones which use a definite 8-bit encoding read/write pascal-style strings with a 16bit length prefix. The ones which use a definite 16-bit encoding read/write pascal-style UTF-16 strings with a 32bit length prefix, i.e. not ByteStrings at all The "I dunno" ones might be UTF-16 strings or 8-bit strings, depending on the charset. Rename to ReadUniOrByteString like the other similar horrors to flag this misery
2011-12-21convert ReadByteString/WriteByteString from ByteString to OStringCaolán McNamara6-101/+169
Nobody ever used the return values anyway, so for reading just return the string and for writing the number of bytes written Doesn't need to be members, make standalone functions Rename to read_lenPrefixed_uInt8s_ToO[U]String and write_lenPrefixed_uInt8s_FromO[U]String, lengthy, but much less unambiguous, seeing as a lot of users of it don't seem to be aware that they read/write pascal-style length prefixed strings, which isn't surprising given the apparent simplicity of their original name. added a unit test
2011-12-19Removed COMPRESSMODE_FULL support from SvStreamMatteo Casalin4-626/+15
2011-12-16gcc-trunk: fix error: unable to find string literal operator 'operator"" FOO'Matúš Kukan2-6/+6
2011-12-15Removed extra semicolonsJesse4-6/+6
2011-12-15add some commentsCaolán McNamara1-2/+6
2011-12-15convert ReadCString from ByteString to OStringCaolán McNamara3-33/+44
Nobody ever checked the return value anyway, so just return the string and use the stream state bits if necessary to find failures. Doesn't need to be a member, make a standalone function Rename it to read_zeroTerminated_uInt8s_AsO[U]String, stupid perhaps, but *shrug*, unambiguous. Drop misleading overloaded String variants use: read_zeroTerminated_uInt8s_AsOString or read_zeroTerminated_uInt8s_AsOUString added a unit test, valgrinded it, found and fixed invalid read in original implementation.
2011-12-15drop unused ReadCString with hidden StreamCharSet monstrosityCaolán McNamara1-1/+0
2011-12-14strip ByteClass down some moreCaolán McNamara2-16/+3
2011-12-12Remove unused macros.Rafael Dominguez1-9/+0
2011-12-12I don't see VCL or NT351 being checked in any ifdefTor Lillqvist1-1/+0
So drop the GVER thing and -DVCL and -DNT351.
2011-12-09callcatcher: remove unused code post automation removalCaolán McNamara6-119/+0
2011-12-07Remove testtoolloaderAugust Sodora4-228/+1
2011-12-07in modules, when we have a env we are in stage gbuildBjoern Michaelsen1-0/+1
2011-12-07use gbuild_simple in toolsBjoern Michaelsen1-2/+3
2011-12-06ditch some ByteStringsCaolán McNamara4-24/+23
2011-12-06aSourceFile member unusedCaolán McNamara1-1/+0
2011-12-05Remove unused tools/stack.hxxMarcel Metz2-104/+0
2011-12-02Also demote DBG_ASSERTWARNING to SAL_INFO, to reduce output clutter.Stephan Bergmann1-5/+5
2011-12-01get rid of class Date and Time default ctor with system time penaltyEike Rathke6-8/+46
2011-12-01pull in module headers before solverEike Rathke2-5/+4
2011-12-01Remove uses of charAtAugust Sodora1-7/+6
2011-11-30introduced Date::IsValidDate() and Date::Normalize()Eike Rathke1-1/+32
+ IsValidDate() checks only day and month regarding the year, not Gregorian cut-off date as now does IsValidAndGregorian(). + Normalize() carries over invalid day and month values to next months and years. * All methods that return or internally use a day count now internally normalize the date values, without modifying the actual Date instance. So, if the date is not valid you may get unexpected results. * Previously, a date with month>12 would had accessed the days-of-month array out of bounds on all such methods. So you would had gotten unexpected results anyway.. * Affected methods are: GetDayOfYear() GetWeekOfYear() GetDaysInMonth() static DateToDays()
2011-11-30introduced Date::IsValidDate() and Date::Normalize()Eike Rathke1-4/+105
+ IsValidDate() checks only day and month regarding the year, not Gregorian cut-off date as now does IsValidAndGregorian(). + Normalize() carries over invalid day and month values to next months and years. * All methods that return or internally use a day count now internally normalize the date values, without modifying the actual Date instance. So, if the date is not valid you may get unexpected results. * Previously, a date with month>12 would had accessed the days-of-month array out of bounds on all such methods. So you would had gotten unexpected results anyway.. * Affected methods are: GetDayOfYear() GetWeekOfYear() GetDaysInMonth() static DateToDays()
2011-11-30renamed Date::IsValid() to IsValidAndGregorian() to prevent misassumptionsEike Rathke3-3/+7
Once smaller than 1582-10-15 decrementing a Date will not produce a valid date.
2011-11-29move reconfigure into gbuildBjoern Michaelsen1-1/+1
2011-11-28ByteString->rtl::OString[Buffer]Caolán McNamara5-96/+72
2011-11-27remove precompiled_xxx.hxx/cxxNorbert Thiebaud2-122/+0
2011-11-27remove pch from the include listNorbert Thiebaud6-6/+0
2011-11-27remove include of pch header from toolsNorbert Thiebaud83-152/+0
2011-11-27remove pre-compiled header support in gbuild and gbuildified moduleNorbert Thiebaud1-2/+0
2011-11-27typos fixingKorrawit Pruegsanusak1-1/+1
2011-11-25typo, thanks Guest70165 :-)Caolán McNamara1-1/+1
2011-11-25ByteString->rtl::OStringCaolán McNamara2-4/+4
2011-11-25make gbuild makefiles run independant of pwd againBjoern Michaelsen1-1/+1
2011-11-25ByteString->rtl::OStringCaolán McNamara4-85/+63
2011-11-25demoted plentiful DBG_WARNING etc. to SAL_INFOStephan Bergmann1-9/+9
2011-11-25gsl_getSystemTextEncoding -> osl_getThreadTextEncodingDavid Tardon1-7/+0
2011-11-24ByteString->rtl::OStringCaolán McNamara1-11/+11
2011-11-24ditch dbg_dumpCaolán McNamara2-51/+0
2011-11-24strip down old string class some moreCaolán McNamara3-58/+32
2011-11-23add string::strip, can replace EraseLeadingAndTrailingCharsCaolán McNamara2-2/+3
generated by cgit v1.2.3 (git 2.39.1) at 2024-09-21 13:37:50 +0000