MessageFormat: Use int64 instead of off_t

They are effectively the same thing, but int64 is more generic.

I used an off_t because that is what Tracker passed in, yet, this could be
used in other places where an off_t doesn't make as much sense.
This commit is contained in:
John Scipione 2015-03-04 15:40:55 -05:00
parent b726ad9203
commit 83d5a5313d
2 changed files with 3 additions and 3 deletions

View File

@ -28,7 +28,7 @@ public:
status_t InitCheck(); status_t InitCheck();
status_t Format(BString& buffer, const off_t arg) const; status_t Format(BString& buffer, const int64 arg) const;
private: private:
status_t _Initialize(const icu::UnicodeString&); status_t _Initialize(const icu::UnicodeString&);

View File

@ -45,7 +45,7 @@ BMessageFormat::InitCheck()
status_t status_t
BMessageFormat::Format(BString& output, const off_t arg) const BMessageFormat::Format(BString& output, const int64 arg) const
{ {
if (fInitStatus != B_OK) if (fInitStatus != B_OK)
return fInitStatus; return fInitStatus;
@ -54,7 +54,7 @@ BMessageFormat::Format(BString& output, const off_t arg) const
UErrorCode error = U_ZERO_ERROR; UErrorCode error = U_ZERO_ERROR;
Formattable arguments[] = { Formattable arguments[] = {
(off_t)arg (int64)arg
}; };
FieldPosition pos; FieldPosition pos;