Slashdot Mirror


80x86 ASM for ASP.NET

Galen Wolffit writes "A chap out in Denmark has brought us an 80386 Assembler for ASP.NET. This interpreter supports about 61 80x86 instructions, though there are a number of limitations. Why? Why not. And when asked about pointers (which are considered evil in .NET), the author simply says 'With 80386 scripting you can still generate memory exceptions and bring the web-server down. It's things like this that make assembler programmers feel powerful.'"

6 of 17 comments (clear)

  1. power? by arnorhs · · Score: 3, Funny

    asm programmers fell powerful whenever they get to write anything... which happens very seldom :/

  2. Overhead? by exebeoex · · Score: 4, Interesting

    I wonder what kind of overhead this incurs. Afterall, for a number of reasons it would only be as fast as an x86 emulator, no? Not to mention trying to convert register based instructions for use on a stack based machine. But maybe this sort of register->stack translation scheme used can be useful for those working on making a backend to the GCC RTL (register transfer language) for the .NET runtime. Could it?

  3. Fun... Perhaps by foooo · · Score: 4, Insightful

    Fun... Perhaps...

    Useful? Probably not.

    I don't personaly find writing Asm to be the quickest way to code something and the benefit of superfast execution speed is lost when converting to IL.

    If you're going to actually write Assembler... do it the way it's meant to be done. Not in .NET... leave .NET to the high(er) level developers it's aimed at.

    ~foooo

  4. Lies! by Tuxinatorium · · Score: 2, Funny

    There is no such thing as x86 architecture! It is a silicon fabrication of the Intel Infidels!

    --(former) Iraqi Information Minister, Mohammed Saeed Al-Sahaf

  5. MenuetOS by e8johan · · Score: 2, Interesting

    Does this mean that we can run MenuetOS on .Net? (MenuetOS is 100% x86 asm)...

  6. This stuff has no effect on the web browser by pchasco · · Score: 2, Informative

    For all those paranoid, you can rest easy. The assembly code still runs on the web server, and not your browser. No different than C# or VB.NET code in that respect. If the web server could force your browser to compile and execute this assembly code, then it could very well just force you to compile and run some C# or VB.NET code.