documentation needs to be added for uwu-fied in-built functions such as:
-pwint()
-inpwt()
also other changes like how pwint() distinguishes between " and ', and also how only "" is accepted by pwint() when pwinting strwings

Title says for itself. Maybe i'll do dome pull requests to fix thi. (anyway why uppercase words for function and etc? don't look really python)

I would like to pwopowose that Contribuwuting in README.md be renamed to Contwibuwuting and similarly contribuwutions to contwibuwutions.

Additionally, request to be renamed as wequest

i think it'll be funny lol

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 wecommend adding s-stuttewing! P-pwease w-weffer tyu watashi's owoifier

I mean, the LISCENCE file says that distribution is allowed...
Project here: https://pypi.org/project/PythOwO/

I think it would be uwumazing if we managed to get pythOwO recognized as a language on Github so it shows on our repos like this:

I've linked some resources I found about how to go about doing this:

• https://docs.github.com/...
• github/linguist

Please mwake mwore languages lwike this UwU

It's gonna be more owosome if it can use owobject like:

cwass Owo:
  fwunction __iwnit__(sweef, nwame, awge):
    sweef.nwame = name
    sweef.awge = awge  

owo1 = Owo("Kawaiowo", 19)

pwint(owo1.nwame)
pwint(owo1.awge) 

I cant compare strings in conditional statements. for example this code produces an error:

pwease baka = "hewwo"
pwease awoo = "hewwo"
IF awoo==baka THWEN pwint("they are equal ") EWSE pwint("twy again")

the error message is

Traceback (most recent call last):
File test.pyowo, line 4, in
owo, whats this? Runtime Error? Oh nwo! : Illegal operation
IF awoo==baka THWEN pwint("yay") EWSE pwint("twy again")
__^^^^^^^^^^

fad

.

Kindly review my PR.
Thewnk UwU

Issue description

When writing code which doesn't capitalize the control flow keywords (to below), the error message is very opaque.

Steps to reproduce the issue

Run the following:

pwease sum = 0
FOR i = 0 TO 5 THWEN
    FOR j = 0 to 3 THWEN
        pwease sum = sum + 1
    END
END
pwint(sum)

What's the expected result?

• If we decide to ignore case on the keywords, then the code should output 15,
• Or the code should yield an error message that at least points to the right area of the code.

What's the actual result?

• The code yields

Owo, whats this? Invawid Syntax? Oh nyo! : Token cannot appear after previous tokens
File exwamples/nwest.pyowo, line 2


FOR i = 0 TO 5 THWEN
^^^

This is a bit of a tall order but I reckon it will be doable. We need to go deeper. Writing the compiler to output Python will probably be most natural, but since the feature set is small (I don't see classes implemented) any language could work. Maybe C so we can actually do a full compilation process and get a working Compiwer binary. Some action steps:

1. Write a working interpreter in a lower-level target language that is restricted to the implemented feature-set of PythOwO
2. Test the compiler thoroughly enough that we can be sure it will translate PythOwO faithfully
3. Finally, translate the compiler to PythOwO
4. Build and ship the Compiwer

For reference, I would recommend looking a little into LoxLox, which is a Lox implementation of the simple language Lox. The only real barrier to implementing it directly is the use of classes. In addition there's the C implementation in Crafting Interpreters, which does fairly well without classes.

Delete this fucking shit and don't disgrace programming, stupid idiots.

It would be good idea to add arrays in the future.