Advertisement

Gateway Scripting

Started by December 05, 2001 09:51 PM
3 comments, last by Andrew Nguyen 23 years ago
I''m working on a ''Game Scripter''. Not a game engine, but a Super-High level lang. It looks like this: thisfile = '' +main |scr = window(145,134,title = ''DEMO'') |PERM: drawin.force.scr @| means statement, kinda like ; but @At the beginning. |print(12,12,''Hi'')@the first 2 args are coordinates. |-MouseClick: @|- means if ...scr.kill ...returnto.os -| @-| means end I call it gateway. Yes, it''s true, there should be a Java-Python-C++ language called Japyc or (Jah-PIC)
---START GEEK CODE BLOCK---GCS/M/S dpu s:+ a---- C++ UL(+) P(++) L+(+) E--- W++ N+ o K w(--) !O !M !V PS- PE+Y+ PGP+ t 5 X-- R tv+ b+ DI+ D G e* h! r-- !x ---END GEEK CODE BLOCK---
Annnnd? The problem is... ?

codeka.com - Just click it.
Advertisement
How is that any more Super-High level than Visual Basic? VB has simpler syntax and can do pretty much the same thing.
You''ll definitely need to work on the syntax. I''d rather read
obfuscated perl code.
For example: |- == if? Why not just use "if" or "IF"? Same
number of keystrokes, and the code would instantly become more
readable.
What is this for? what type of game? Do you want to run the scripts quickly?

I''ve done a bit of work on createing a scripting language....what helps is to design it around an ''imaginary processor'' that your game code emulates...that is if you intend it to be reasonably quick to execute and powerfull enough to be used in a variety of ways (besides poping open new windows, etc..)

I designed an imaginary 8-bit processor that had a special memory system and system of ''interupts'' available to it (and simple 256 byte stack machine)...I then designed a simple "assembly" like language that would work with it (actually through series of functions)...then rather then write scripts in this simple assembly code..I wrote a very basic "compiler" that would read through a text file and compile a self designed high level scripting code into the "assembler" I designed...by linking the ''compiler'' to a simple data base...I could easily add/remove scripting language keywords and thier "assembler" opcode constructs...and by useing the same database a "decompiler" could be written to find bugs, etc... worked pretty well too...but I would do it different now as I understand more about how processors work

This topic is closed to new replies.

Advertisement