pythOwO
pythOwO copied to clipboard
virejdasani
rules to UwUfwicatwion?
what if we define some rules so that we can identify when to use "uwu" and "w" during uwufwicatwion? so suppose we have 3 words, number, please, math they get uwufied as: number -> nuwumber please -> pwease math -> mathowo (source: calcuwulator.pyowo)
setting some rules would help future contributors during uwufwicatwion, n will prevent over/under uwufwicatwion at times :3
I've honestly been thinking about this idea for a while.
Uwufication has some de-facto standard pattern that it already follows:
- any
uis substituted with anuwu - any
landris substituted with aw(we don't take L's here) - not sure about
owo, we might need to clarify where that applies..
This could be enforced with a linter, formatter, or the language itself to ensure UwU compliancy. Maybe we should start a project on that? A wintew?
Another rule I thought might be in line with this might be requiring that every function name must start (or maybe end) with an owo, like a function named add must be named owoadd (or maybe addowo).
yes i love the idea of a linter for pythOwO
as for owo , u can add it to nouns that were exempted from the previous 2 mentioned rules, i.e., they don't have any u, l or r. Such as math, so in this case, owo just gets added to its end
So writing a BrainFuck interpreter for a demo turned out to be beyond the language's capacity within the time I had to work on it today. I also discovered the hard way that a linter is not very easy, even harder when determining what is and is not a noun. I did however manage with the time I had left to write an example function in pythOwO which takes a character and returns a string that substitutes it, which accomplished some of the patterns discussed here (everything but owo).
In the future this could be used towards implementing a full-blown linter and bootstrap compiler, but for the moment the language limitations prevent that.