You are not logged in.
Pages: 1
@NTAuthority - guess you know, but anyway
http://www.joncaruana.com/projects/point/scm_api.xmlan attempt of making a xml-based opcode list
Yes, I knew about the Point implementation already -- that was one of the inspirations for my list, which was meant to eventually be used by a SA SC syntax compiler/IDE as 'fully-documented' file.
Also, in the IV, we have real opcode/native names. Maybe, one day, someone can map SA opcodes to the real names, e.g.
*snip*
and so on.
I once started on making a list of command names for SA, but quit due to it being a large task. Starting at III might be a lot easier? Another things I have in my mind is a lot of information about the .sc source code format, both for III/VC, SA and a bit of IV -- I really ought to document my information on it someday.
For who's interested in these old ugly lists, see the two things posted on pastebin (made before I started looking through disassembly, though):
http://pastebin.com/p0Vi9QT1 - old list
http://pastebin.com/iSqbjygS - some advanced XML format with documentation built in
PS. Did you see http://public.sannybuilder.com/sources/ … 090822.rar ?
Ah, yes, OpenSA was another thing inspiring some 'likely never to be implemented idea' of mine -- something like header files for 'plugins' with normal 'real' functions but then having stuff mapped to the locations as seen in the compiled code... Also, I should really look more into internal code for IV, my main information is based on continuation of the SA IDB and III IDB found on public.sannybuilder.com and 'common knowledge'.
Pages: 1