Last modified: 2014-09-23 19:58:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42087, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40087 - ParserFunctions: bad exponentiation syntax should raise an error
ParserFunctions: bad exponentiation syntax should raise an error
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
master
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
https://en.wikipedia.org/wiki/User:WO...
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-07 18:02 UTC by Derk-Jan Hartman
Modified: 2014-09-23 19:58 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Derk-Jan Hartman 2012-09-07 18:02:41 UTC
Mwlib seems to be unable to handle the following:

{{#expr:(1E5round0)E5}}
Comment 1 Derk-Jan Hartman 2012-09-07 18:05:37 UTC
Filed upstream (i think it's number is 3546)
Comment 2 Ruslan 2012-09-09 11:07:17 UTC
In fact an error appears in any expression that contains parentheses () before E operator: {{#expr:(1)E5}}. It can be fixed by inserting multiplication:  {{#expr:(1)*1E5}}.
Comment 3 Ralf Schmitt 2012-09-21 20:14:12 UTC
really guys, e shouldn't be an operator. this is just braindamaged.

thinks like "e e e" and "1e2e5" should raise a syntax error. the current mediawiki version evaluates them happily. wtf!

I've implemented that in mwlib.

I'm setting the component to ParserFunctions, since this issue should really be fixed there.

please read https://en.wikipedia.org/wiki/Scientific_notation
Comment 4 Sumana Harihareswara 2012-12-14 15:03:53 UTC
Pinging Umherirrender in case you want to make an attempt at fixing this issue in ParserFunctions.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links