Hey guys, so its been a while I’ve got a lot of stuff done and many core things working in Gccpy now more links on how to get up and running with it soon.
I am asking for help from you or from your friend.. anyone, all you need is:
- 5 minutes
- text editor
- basic knowledge in python
I am trying to build up a test suite for this compiler and i would love to have it all built from scratch for this project rather than taking something from CPython where i think licenses will clash and i want to avoid anything like that. So what does this all mean?
I need people to write up their favourite python snippets, but there are requirements: what you can do is use anything EXCEPT any imports. Imports are something which will be handled soon, and isn’t that importantĀ yet for the core language implementation.
So I have set-up this mailing list and i would love it if as many of you would join: http://crules.org/cgi-bin/mailman/listinfo/gccpy
So join the mailing list or simply post a message if you prefer and we will try to remember to cc you with in. One thing i would ask is only submit a small test case if you are ok with this being pretty much un-licensed because GNU projects require copy approval for you to submit code, but we can negate this by going though me just submit this to me under a http://sam.zoy.org/wtfpl/ (Whatever you want to do license) . This just saves any pain of licensing, you will of course still be attributed! Leave your name and an email within the test-case file, since really that’s all we care about as hackers anyway we don’t care about licensing so long as we have some attribution. To give you a flavour of how simple these test cases can be lets look at one i made earlier:
-
# DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
-
# Version 2, December 2004
-
#
-
# Copyright (C) 2004 Sam Hocevar
-
#
-
# Everyone is permitted to copy and distribute verbatim or modified
-
# copies of this license document, and changing it is allowed as long
-
# as the name is changed.
-
#
-
# DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
-
# TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
#
-
# 0. You just DO WHAT THE FUCK YOU WANT TO.
-
#
-
-
# @Author redbrain – redbrain@gcc.gnu.org
-
# @Date 13/8/10
-
# @Expected Result: <5>
-
# -Tested against Python Version <2.6.5>
-
-
def foo ( x , y ):
-
return x+y
-
-
print foo( 2,3 )
Things for testing the expression syntax handling or calling functions, parameter passing like keywords parameters and positional parameters, class’s anything! Even if it is as small as one expression and a print for the result it is more than enough for a test case! The reason I want as many people involved is so i can see what features/trends matter most important to python users and then I can focus on making them extra awesome. And if it only takes you 5 minutes to write a small piece of python code and send an email while you get your name within the Gcc sources the more the better:).
When you create a test case simply send an email to the mailing list with the subject “Test Case <name>”. You can submit as many as you like the more the betterĀ and the funnier the better…. * looks at Jezra
! @yamatt i am reusing that python while loop you sent me ages ago to freak out my processor!
Thanks so much every one, watch this space in the next week for links on how to use and see your test case running in Gccpy, so you can compile your python code to an executable!
So remember the mailing list is over here. http://crules.org/cgi-bin/mailman/listinfo/gccpy










expect a pointless piece of script soon….