User talk:Javamannen

From Esolang
Jump to navigation Jump to search

Can you send me your e-mail address? --Oleg 07:19, 13 October 2010 (UTC)

I sent you an email. --Javamannen 19:21, 13 October 2010 (UTC)

Re: BytePusher VM

The audio works a lot better now. Thanks for updating your VM. Now we just need a test which isn't so irritating (yes AudioTest.BytePusher is starting to drive me nuts). I might make a MOD player. --Ben Russell 01:10, 18 October 2010 (UTC)

If you think this one is irritating you should have heard the original version... Anyway, a MOD player would be great! That's the kind of app BytePusher was designed for. And you get that grungy Amiga-esque lofi quality for free =) Actually, it's even better: It's in Mono! =P --Javamannen 05:09, 18 October 2010 (UTC)

Verilog/VHDL BytePusher implementation

I'm interested in implementing a Verilog/VHDL version of the BytePusher VM for FPGA implementation. Someone interested in helping out with non-FPGA questions? Send me an email. --Overclocked 12:18, 9 September 2011 (UTC)

Because of the BytePusher machine code not being as dence as ByteByte/Jump machine it is not the perfect choice for FPGA in which memory handling is somewhat limited and cumbersome for home users. For the "average" FPGA-home-user to be able to work/port a BytePusher-core to their own boards, usually SRAM (256-1024Kbyte) or FPGA own built-in RAM, BlockRAM(maybe 20kByte-100Kbyte) should be used. Thoughts on this? It is not stopping me implementing it in the near future.. :-) --overclocked 11:13, 30 March 2012 (UTC)

Feature request

To make BytePusher more usable "moving" forward I would to propose a new keyboard input register to be use with normal keyboards (ASCII codes or keycodes). This way it would be possible to implement a console and more nice stuff. Today it too simplified with its 16 keys I think making input a weak point and possible applications limited. Another suggestion would be to lock the whole first PAGE (address: 0x0-0xFF) for future system use and maybe to use a version register too be able to add stuff. Because of alignment of tables in PAGE's/BANK's this would fit quite nicely to the rest of the platform. A disadvantage is that all BytePusher-programs probably would need these 256 bytes within them, making the minimal BytePusher-program size 256 bytes.. Problem? This request comes from the fact that I'm working on a new tool for implementing programs for BytePusher.. more later! --overclocked 11:13, 30 March 2012 (UTC)

Moved two sections to this page


I noticed your user page was being used as a talk page a lot, so I've split the discussion sections up and moved it here.

Hope you don't mind :) —ehird 23:10, 11 September 2011 (UTC)

Where are you?

Did you left esolang wiki? --mlkstd (talk) 11:05, 14 May 2020 (UTC)