On 23/11/12 10:15, Jeroen De Dauw wrote:
> Hey,
>
>> Interesting. How does that work?
>
> Use the source, Markus... :)
>
> https://github.com/wikimedia/mediawiki-extensions-SemanticResultFormats/blob/master/formats/math/SRF_Math.php#L83
Not very helpful. I know I can dig into source code to find o
Hey,
> Interesting. How does that work?
Use the source, Markus... :)
https://github.com/wikimedia/mediawiki-extensions-SemanticResultFormats/blob/master/formats/math/SRF_Math.php#L83
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
-
On 22/11/12 11:22, Yury Katkov wrote:
> The premises are clear:
> (1) the current implementation of the max parser function is slow and
> (2) there is a workaround for making max queries quicker.
>
> The conclusion is not clear: "let's drop the max ASAP".
>
> It's not that hard to replace the curr
On 22/11/12 14:44, Jeroen De Dauw wrote:
> Hey,
>
> Markus, I agree with you that in most cases you're better off doing a
> sorted query, and think this should be reflected in the documentation.
> I however would not be to quick to conclude the max format is
> completely useless. For one thing it s
Hey,
Markus, I agree with you that in most cases you're better off doing a
sorted query, and think this should be reflected in the documentation.
I however would not be to quick to conclude the max format is
completely useless. For one thing it supports recursion when dealing
with containers. Peop
The premises are clear:
(1) the current implementation of the max parser function is slow and
(2) there is a workaround for making max queries quicker.
The conclusion is not clear: "let's drop the max ASAP".
It's not that hard to replace the current implementation of MAX format
with the faster o
