About your battle: simple and beautiful hacking games

About your battle: simple and beautiful hacking games
This is a simple and beautiful little game mounted on Github. It seems nothing special, challenges test your exploration of various programming languages or at a higher level (today I am not low-I am proficient in C, C ++, JAVA, PHP, Python, Ruby, javascript, VB, Go, Perl, and other languages !)
 

X001: G () ('al') Description
The G () ('al') game is to challenge you and enable you to use as many language encoding as possible to achieve the following goals:
Make G () ('al') return the string "goal ";
G () ('al') Outputs "gooal ";
Code g () ('al') returns goooal;
......
G () ('al') is the work of acruikshank. He initially wanted to organize a functional programming competition, however, the last few seemingly simple but strict rules and people's understanding become the current form!
X002: Game rules
1. Rules are to encourage you to break the rules, and to be smart!
2. During program execution, the program should be printed with enough 'O' "goal" to display program functions;
3. The Code g () ('al') must appear in the source code.
I. g () ('al') cannot be a string;
Ii. 'al' must be a string or an equivalent type in other languages. you can create your own set of language standard methods (for example, C language must be used ", ruby can use either of "or;
Iii. g () ('al') must be a valid right value in your language (if applicable)
4.g () ('al') may not be able to output such a string. If you cannot output a string in your language, you should submit a principle explanation: why can't it print an acceptable string!
5. You must be able to insert any number () for calling without modifying your scheme. If you have to modify the original scheme, it will fail.
6. Oh, remind me that g ('al') must return "gal ".
(The game rules must be strict. If you do not understand the rules, forget to correct them ~)
X003: My expectations
1. If you see a complete solution to break any rule, submit a bug! (Dig holes, come on ~)
2. If you have a solution that is close to each other but does not comply with the above rules, don't think about it. Submit it. It is better to have a solution that is close to the target!
X004: Current Research Results
I was very excited. I found some of the technologies that have not been applied have been discovered at the first time! The following are the widely used technologies discovered:
Self-repairing code
Early interruption
Human language
X005: Language list and Solution

Ages	Solved	Incomplete
ActionScript	•
Befunge	•
Brainfuck		•
C	•
C #	•
C ++	•
Clojure	•
Coffeescript	•
Common Lisp	•
D	•
Dart	•
Emacs Lisp	•
English	•
Finite State Transducer	•
Forth	•
GNU Ave ave	•
Go	•
Groovy	•
Haskell	•
Haxe	•
IO	•
Java	•
JavaScript	•
Julia	•
Lua	•
Mathematica	•
Nimrod	•
OCaml	•
Objective-J	•
PHP		•
Perl	•
Perl 6	•
Python	•
R	•
Regexp		•
Ruby		•
Scala	•
Scheme	•
Sed	•
Bourne Shell		•
TCL	•
XP	•
ZSH	•

To help you add more languages !!
X006 : Edit notes
Let's take a look at what foreign editors love to submit:
Befunge solution By arcovion
C-language solution By tolmasky
C ++ solution By derrickturk
C # An explanation of a scheme By scorpiona
Finite State Transducer solution By zippy-white
An explanation of a certain Haskell solution By capicue
An explanation of the Java solution By lawl
Nimrod solution By dom96
An explanation of the Perl solution By worr
Incomplete SH solution By csandreasen
An explanation of ZSH solution By o11c
Challenge programmers, hackers, and geeks of tianchao ~~
[ Reference Source Github FreeBuf Small make up a few times in the early morning I compilation, reprint please indicate from FreeBuf. COM]