This is anarchive of past discussions.Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on thecurrent talk page.
Latest comment:1 year ago8 comments4 people in discussion
Function created by @RuzDD. Seems to be done for testing and learning purposes. The implementation seems to be copy and pasted from somewhere, and tries to run Flash from a given source, which is nothing we currently support. Implementation is here:Z13080, and should be deleted too. --Denny (talk)18:18, 14 June 2024 (UTC)
I did not know the exact purpose of Wikifunctions and you may be right, but I did not copy the implementation from somewhere. Why you think I was copied the implementation from somewhere @Denny? I never made edits with copyvios. (By the way, even if won't be deleted, I should largely edit this implementation to make it not use Ruffle if the browser asks for permission.)RuzDD (talk)08:08, 18 June 2024 (UTC)
@RuzDD: Apologies, I did not mean any disrespect. I now read up on the April discussion, and sorry I missed the discussion back then. But yes, this does not align with the current capabilities of Wikifunctions, nor will it for a long while. Thanks! --Denny (talk)19:24, 18 June 2024 (UTC)
We discussed this function as RuzDD was creating it backhere. Because it doesn't match what Wikifunctions is capable of, I suggest we delete this and you try some simpler functions more similar to the ones we already have working. --99of9 (talk)13:10, 18 June 2024 (UTC)
Latest comment:1 year ago3 comments2 people in discussion
Is using "byte" instead of "natural number" as the type for the second argument, and "codepoint" instead of "string" for the third argument. I was planning to fix it up, but then discovered that we already haveZ14770, which is using exactly these argument types. So I moved the missing labels from Z10093 to Z14770, also switched the JS implementationZ10094 from Z10093 to Z14770. The Python implementations of both functions,Z14772 andZ10107 are the same (modulo a bug). Therefore I suggest to also deleteZ10107. There are no tests to be brought over. --Denny (talk)21:22, 14 June 2024 (UTC)
Latest comment:1 year ago4 comments2 people in discussion
I accidentally made this with the wrong signature. It is suppose to take an object and a key reference but I accidently only put the object as the inputScienceD90 (talk)01:13, 23 June 2024 (UTC)
But it may sometimes be easier to read an object with a label instead of a string literal, or tell the intention better. I am a bit torn about such literals, I really don't know. I for sure do not have a principled stand on this yet. (Note that this comment is explicitly in my hat as a volunteer). --Denny (talk)15:03, 17 June 2024 (UTC)
The interface should distinguish between different code points that are currently displayed as "". In the meantime, I guess it is convenient to have a literal Z6 for each invisible code point that is used in a composition or test case. (I feel a new implementation ofZ10008 coming on…Z17075.)
In any event, I do not believe that an object should be formally proposed for deletion on this page without a notice on its own talk page that notifies its watchers of what is proposed (except for recently created objects that fall into the categories listed in the first paragraph of this page). Perhaps we should have a “Consider for deletion” section or page?GrounderUK (talk)10:42, 18 June 2024 (UTC)
Keep. I think it helps to have examples of a handful of hardcoded objects of each type. They are easily accessible viaSpecial:ListObjectsByType. This one is also especially useful for making compositions more readable. One slight concern is that a vandal could change the underlying object, and break multiple functions. So I'd actually favour some kind of page protection on it. --99of9 (talk)00:06, 30 August 2024 (UTC)