-.kt

# announcements

[Smallville7123]

-.kt

-.kt

[Nate]

when(it) {
  "", "-h", "--help" -> printHelp()
}

would be a start

[Smallville7123]

oh ok

[Smallville7123]

yay its all clean now ^-^
https://kotlinlang.slack.com/files/UH83T3WAE/FHYFQAX5W/-.kt

[Katie Levy]

I would extract the when portion into another function like processOption(option: String)

[Katie Levy]

fun main(a: Array<String>) {
    if (a.isEmpty()) processSTDIN()
    else a.forEach {
       processOption(it)
   }
}

[Smallville7123]

wouldnt that be redundant?

[Katie Levy]

I like modularizing my code to make it more concise and more easily testable

[Smallville7123]

oki

[Smallville7123]

well i only need it for main() so... : P

[Smallville7123]

plus it isnt like it is meant to be a full library version of a program like git("--clone $URL") or something, so i dont see a need to modulize its argument parsing nor add it to the library itself

[Smallville7123]

but i love modularizing ^-^

[Nate]

How would you do the a.size == 1 check in that case?

[Smallville7123]

one day i want to make a modularized VM lol

[Smallville7123]

eg, where you can actually construct your own VM or create one from hardware presets

[Smallville7123]

just like you would in the real world lol

[Smallville7123]

that would be epic asf

[Smallville7123]

but current VM's dont support this ;-; as they only focus on emulating a particular architecture

[Smallville7123]

or the lack of flexibility of hardware the VM is based on, thus if you want to support a new or existing architecture the entire VM will need to be re-written to target that architecture

[Smallville7123]

its just all super complicated and not user friendly lol

[Smallville7123]

eg, id like it to be something like

vm(
    cpu = cpu(
        architecture = "x86",
        model = "generic",
        cores = 4
    ),
    gpu = gpu(
        model = "generic",
        memory = 512,
        size = "MB"
    ),
    ram = ram(
        memory = "1"
        size = "GB"
    ),
    components(
        keyboard = generic,
        screen = generic,
        mouse = none
    )
).run(kernel)

[Smallville7123]

unfortunately the problem with that is hardware documentation vs ISA size

[Smallville7123]

as ARM alone has about 700 instructions in its ISA

[Smallville7123]

intel x86 about 1.2k i think

[Smallville7123]

i do have a alpha version though https://github.com/mgood7123/ccr_resources/tree/master/Scripts/vcpu/MOTOROLA/MC680X0

[Smallville7123]

but its far from complete

[Smallville7123]

i do have a small test model that works https://github.com/mgood7123/ccr_resources/blob/master/Scripts/vcpu/intel_4004.c

[Katie Levy]

That's awesome, keep working at it!!

[Smallville7123]

i gave up on that lol

[Smallville7123]

mainly due to lack of hardware documentation for the AMIGA systems required for emulation

[Smallville7123]

that my chosen CPU runs on

[Smallville7123]

(the CPU has roughly 100 to 102 instructions, and is capable of running the linux kernel with full memory managment (MMU) support)

[Smallville7123]

in which a Memory Managment Unit is REQUIRED by linux in order to support running multiple programs, otherwise only one process can run at a time, including the kernel itself

[Smallville7123]

anyway, its abandoned due to the extreme lack of documentation for the AMIGA hardware required for the VM to emulate the hardware that the cpu is compatible with

[Smallville7123]

for example, did you know that almost EVERY hardware that at least has a CPU and RAM requires a memory map (as in what regions of RAM are dedicated to X component/hardware/software/whatever)