Oh, yeah. I guess that could be an issue. We're using a standardised language so all android models have a certain amount of compatibility. Makes it easier to maintain.
[A hard light screen appears at roughly shoulder height with his schematics. His model is listed as YoRHa Number 9 Type S.
Along with the diagrams, it lists his physical details as well as most of his functions. Many of the latter comprises of obvious basics, such as control over motor functions, visual systems, memory systems, and sound input/output, but there are some less obvious ones that are listed as "black box system", "near field control system" (NFCS), "far field control system" (FFCS), and the like. It's also apparent from the schematics that despite appearances, his 'skin' is comprised of nanomachines capable of minor self-repair. Also listed is a hacking module.
A second screen appears with his programming language, easily scrollable.]
Anyway, if you give me a copy of the language and libraries you use, I should be able to incorporate it into my systems. I'm a scanner, after all!
no subject
[A hard light screen appears at roughly shoulder height with his schematics. His model is listed as YoRHa Number 9 Type S.
Along with the diagrams, it lists his physical details as well as most of his functions. Many of the latter comprises of obvious basics, such as control over motor functions, visual systems, memory systems, and sound input/output, but there are some less obvious ones that are listed as "black box system", "near field control system" (NFCS), "far field control system" (FFCS), and the like. It's also apparent from the schematics that despite appearances, his 'skin' is comprised of nanomachines capable of minor self-repair. Also listed is a hacking module.
A second screen appears with his programming language, easily scrollable.]
Anyway, if you give me a copy of the language and libraries you use, I should be able to incorporate it into my systems. I'm a scanner, after all!