Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Strategy Game Collaboration

Name: =+=*=F=R=O=Z=E=N==V=O=I=D=*=+= !frozEn/KIg 2009-07-19 0:46

Experimental RTS/Space sim Collaborative Coding Project.
The goal is to design a game with structure/settings/balance of Starcraft and scale of Eve Online(i.e. huge space battles, space empires,etc).
Though this wouldn't stop anyone from contributing code/feedback/criticism, i'll be coordinating the project.
All code/ideas should be posted in this and subsequent threads which i'll start as needed.
step #1: We will collaboratively create a name for our project.
Each suggestion must explain why this name fits the project and why its better then any other generic name.

Name: Anonymous 2009-07-22 16:42

>>501
Sure, but there is no need for core.bin to translate file.lisp to file.bin, if you tree-shake the core file, it will only contain the functions your application needs. If such functionality is similar to what you would require of a libc, there is no need for this file to be large at all.

".bin"/.core/.fasl is supposed to be a non-standard object file format (similar to obj or dll) containing native code, which can be mapped into memory and run directly by the CPU/OS.

A VM in a more correct definition, has to execute some sort of bytecode, but in this case, the small loader doesn't execute any bytecode, all it does is map executable native code into memory and just lets the CPU run it.

A better analogy can be made here:
Think of .obj files produced by your C compiler as similar to .fasl or .core.
Think of sbcl.exe as link.exe which write to memory instead of an executable.

The analogy is not technically correct, as the structure of those 2 formats differs widely, however both do contain native executable code which is meant to be ran directly, and link.exe does not provide garbage collection or exception handling, but the general concept still applies.

Newer Posts