Skip to main content
13 events
when toggle format what by license comment
May 23, 2014 at 6:50 comment added Eric Lippert @dhams: A device is any thing made for a particular purpose. Every compiler I've ever written was run on hardware that was purpose-built to allow compilers to exist.
May 23, 2014 at 6:47 comment added dharmendra @EricLippert Compiler is not a device , device is something contains hardware.we can say a predefined program which having a set of rules to convert input data in to machine code
Sep 23, 2013 at 19:16 history edited Eric Lippert CC BY-SA 3.0
added 50 characters in body
Jul 9, 2011 at 3:36 comment added Eric Lippert @Cyclotis04: Inform6 compiles to Z-code, which is a famous extremely early example of a bytecode-based virtual machine. That's how all those Infocom games in the 1980s could be both larger than memory and portable to multiple architectures; the games were compiled to z-code and then z-code interpreters with code memory paging were implemented for multiple machines. Nowadays of course you can run a zcode interpreter on a wristwatch if you need to, but back in the day that was high tech. See en.wikipedia.org/wiki/Z-machine for details.
Jun 17, 2011 at 18:13 history edited Eric Lippert CC BY-SA 3.0
added 176 characters in body
Jun 16, 2011 at 21:21 history edited Eric Lippert CC BY-SA 3.0
added 380 characters in body
Jun 16, 2011 at 20:32 history edited Eric Lippert CC BY-SA 3.0
added 272 characters in body
Jun 16, 2011 at 20:25 history edited Eric Lippert CC BY-SA 3.0
added 589 characters in body; added 377 characters in body
Jun 16, 2011 at 18:08 history edited Eric Lippert CC BY-SA 3.0
deleted 12 characters in body
Jun 16, 2011 at 13:31 history made wiki Post Made Community Wiki by Michael Ekstrand
Jun 16, 2011 at 13:19 comment added Eric Lippert @Thorbjørn: Let's be clear about the terminology. A "compiler" is any device that translates from one programming language to another. One of the nice things about having a C# compiler that turns C# into IL, and an IL compiler (the "jitter") that turns IL into machine code, is that you get to write the C# compiler to IL (easy!), and put the processor-specific optimizations in the jitter. It's not that compiler optimizations are "not being done", it's that the jit compiler team does them for us. See blogs.msdn.com/b/ericlippert/archive/2009/06/11/…
Jun 16, 2011 at 8:48 comment added user1249 Have you written about to what degree compiler optimizations are not being done anymore as the CLR can do them automatically?
Jun 15, 2011 at 23:19 history answered Eric Lippert CC BY-SA 3.0