+- Forums - Open Redstone Engineers (https://forum.openredstone.org)
+-- Forum: ORE General (https://forum.openredstone.org/forum-39.html)
+--- Forum: Build Discussion (https://forum.openredstone.org/forum-50.html)
+--- Thread: Standards/Protocols Discussion (/thread-1757.html)
Standards/Protocols Discussion - xdot - 12-28-2013
(12-28-2013, 06:37 PM)Frontrider Wrote: Maybe a new thread where everyone has one post to write down what codes he using?
So, discuss and suggest minecraft protocols.
TODO:
- Standard ORE Instruction Set
- Standard Serial Data Transfer Protocol
- Display/GPU Protocol/Standard
- Classification of Instruction Sets
- Classification of data transfer protocols
- Character Encoding (7-bit ASCII?)
- Network Packet Routing
- Network Streams (Simplified TCP?)
NOTE: This post will be updated in the near future.
RE: Standards/Protocols Discussion - Chibill - 12-28-2013
Only a standard IS that it needs to be able to use but can have a custom one.
Like it interputs the Standard IS.
Also for protocals we need to have a standard type of communication then a protocol but I say 4 bit segments.
RE: Standards/Protocols Discussion - himehowareu - 12-28-2013
I think that standard IS would be a limit the possibility for redstoning but I think it should be a contest for the internet protocols should be held .
RE: Standards/Protocols Discussion - mort96 - 12-28-2013
I think, with the speed of minecraft CPUs, interpreting an instruction set would be a huge overhead. I think we should choose one IS as the "ORE x86", the IS most CPUs use and most software is written for.
I wrote a specification for an IS which I think is pretty neat: http://mortie.org/?webapp=compiler_16/morcore_spec.txt. It should be fairly easy to implement.
Another plus is that I've already written a compiler for it, http://mortie.org/?webapp=compiler_16. If we went with that IS, all CPUs implementing it could be programmed via that web app.
I don't know if my IS is necessarily the best to choose for a standard IS, but it's at least out there.
RE: Standards/Protocols Discussion - WrytXander - 12-28-2013
(12-28-2013, 10:28 PM)mort96 Wrote: I think, with the speed of minecraft CPUs, interpreting an instruction set would be a huge overhead. I think we should choose one IS as the "ORE x86", the IS most CPUs use and most software is written for.
I wrote a specification for an IS which I think is pretty neat: http://mortie.org/?webapp=compiler_16/morcore_spec.txt. It should be fairly easy to implement.
Another plus is that I've already written a compiler for it, http://mortie.org/?webapp=compiler_16. If we went with that IS, all CPUs implementing it could be programmed via that web app.
I don't know if my IS is necessarily the best to choose for a standard IS, but it's at least out there.
I really love the IS, but one thins that bugged me, was the fact that there were stacks. Not everyone uses stacksor know how to use/implement one. So mysuggestion would be having two versions of this IS, one being a simple one, the pther being a more complex yet broad one. The basic OPs would be the same, so they could easily talk to each other.
Another suggestion would be, maybe we could use already existing ISs, that were probably made for educational purposes, such as RiSC16 or something.
RE: Standards/Protocols Discussion - Iceglade - 12-28-2013
(12-28-2013, 10:28 PM)mort96 Wrote: I think, with the speed of minecraft CPUs, interpreting an instruction set would be a huge overhead. I think we should choose one IS as the "ORE x86", the IS most CPUs use and most software is written for.
I wrote a specification for an IS which I think is pretty neat: http://mortie.org/?webapp=compiler_16/morcore_spec.txt. It should be fairly easy to implement.
Another plus is that I've already written a compiler for it, http://mortie.org/?webapp=compiler_16. If we went with that IS, all CPUs implementing it could be programmed via that web app.
I don't know if my IS is necessarily the best to choose for a standard IS, but it's at least out there.
Could you make a thread going more in depth on how to code for that? It looks interesting and if we were to standardize then it would be good to know.
RE: Standards/Protocols Discussion - mort96 - 12-28-2013
@ice added some documentation to the site now.
@wryt not so sure about using IRL ISes. IRL, there really isn't an issue if you have to use 10 commands instead of 5 to do a task, as even on the slowest computers, there would be no significant difference. In MC however, that could be almost a minute difference on a slow-ish CPU.
There's also the memory issue. Minecraft CPUs usually have 4, 8 or 16 registers, and no external RAM. Compilers for minecraft CPUs therefore have to be really careful about how much RAM it uses. My Sixteen compiler mostly directly translates from Sixteen code to Morcore binary, with some syntactic sugar. I fear that to get something similar with IRL educational ISes, we would have to both use a lot more instructions and more registers. I may be completely wrong about this though, I'm not an expert in the field.
I really don't think multiple variations of the standard IS would be a good idea. Even though they would be similar, a lot of software would for instance require stacks, which would make it unusable in all CPUs which don't have stacks. Rather remove stacks completely than leave them optional to the CPU producer.
RE: Standards/Protocols Discussion - Frontrider - 12-28-2013
I suggested this thread, so i may tell my opnion: 3 or 6 bits, i dont think that its matters in binary, but its really matters in my system.
forum.openredstone.org/showthread.php?tid=1701
Matters to me as long as orders for non boulen logic can be repredented in these bits. Base 8 can make compact and fast circuit, count it in while deciding.
I will accept whatever you say, but count it in.Make sure that your codes will not be a drawback. I think this is the reason why people dont like it, but if you make it flexible, then it will bring forward.
RE: Standards/Protocols Discussion - mort96 - 12-29-2013
I had actually pushed some changes with no testing. It broke everything, and I didn't notice. Way to go. The Sixteen compiler should now work.
RE: Standards/Protocols Discussion - Chibill - 12-29-2013
Down with Standard Do you not remember what happened when we tried this on the RDF.