Issue 52064 - Addition of new parse type for parsing integer not, real number
Summary: Addition of new parse type for parsing integer not, real number
Status: ACCEPTED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: http://api.openoffice.org/docs/common...
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-16 22:09 UTC by kyoshida
Modified: 2017-05-20 11:27 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description kyoshida 2005-07-16 22:09:06 UTC
An addition of a new parse type for dealing with an integer, not a real number,
would be useful.

Such parse type could be named, say, KParseType::ANY_INTEGER or
KParseType::ANY_INT_NUMBER, or similar.  It is essentially the same as
KParseType::ANY_NUMBER, except it treats a decimal separator as a non-number
under all conditions.

I've filed this issue because I couldn't find any way of parsing just an integer
using parsePredefinedToken.  Doing so with KParseType::IDENTNAME and
KParseToken::ANY_NUMBER as the start and con token types seems to work, but I
have to manually covert a string segment to double using
rtl::OUString::toDouble(), instead of getting the value from ParseResult.Value.

So, an addition of an integer parse type would be very nice.

Thanks,

Kohei
Comment 1 ooo 2005-08-03 16:53:06 UTC
Hi Kohei,

I second this, could be useful. Hope we don't run out of bits for the flags ;-)

  Eike
Comment 2 ooo 2006-07-20 13:47:40 UTC
Targeting to 2.x
Comment 3 Martin Hollmichel 2007-11-09 17:27:47 UTC
set target from 2.x to 3.x according to
http://wiki.services.openoffice.org/wiki/Target_3x
Comment 4 Marcus 2017-05-20 11:27:46 UTC
Reset assigne to the default "issues@openoffice.apache.org".