The comp.compilers article index for Jan 2011

| Previous month | Next month | Month index|


Compiler positions available for week ending January 30 compilers@iecc.com (comp.compilers) (2011-01-30)
FAKE CONFERENCE: The 2011 International Conference on Foundations of C amgsolo@yahoo.com (A. M. G. Solo) (2011-01-29)
Re: Intermediate forms (again?): worthwhile? cr88192@hotmail.com (BGB) (2011-01-26)
Re: Intermediate forms (again?): worthwhile? bc@freeuk.com (Bartc) (2011-01-26)
Re: Intermediate forms (again?): worthwhile? eh@electrichedgehog.net (Chris Dollin) (2011-01-26)
Re: Intermediate forms (again?): worthwhile? thomas.mertes@gmx.at (tm) (2011-01-24)
Re: Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-24)
Re: language design implications for variant records in a pascal-like martin@gkc.org.uk (Martin Ward) (2011-01-24)
Re: Intermediate forms (again?): worthwhile? barry.j.kelly@gmail.com (Barry Kelly) (2011-01-24)
Re: Intermediate forms (again?): worthwhile? steshaw@gmail.com (Steven Shaw) (2011-01-24)
Re: Intermediate forms (again?): worthwhile? steshaw@gmail.com (Steven Shaw) (2011-01-24)
ANN: bigloo3.6a Manuel.Serrano@Inria.fr (Manuel Serrano) (2011-01-24)
Re: Intermediate forms (again?): worthwhile? bc@freeuk.com (Bartc) (2011-01-23)
Searching for a C/C++ Interpreter written in pure Java steshaw@gmail.com (Steven Shaw) (2011-01-23)
Publications on region based and C++ specific optimizations cbergstrom@pathscale.com (=?ISO-8859-1?Q?=22C=2E_Bergstr=F6m=22?=) (2011-01-23)
Re: Flex 2.5.35: fatal flex scanner internal error--end of buffer miss clint.olsen@gmail.com (Clint O) (2011-01-22)
Flex 2.5.35: fatal flex scanner internal error--end of buffer missed clint.olsen@gmail.com (Clint O) (2011-01-22)
Re: Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-22)
Re: Intermediate forms (again?): worthwhile? ehog.hedge@googlemail.com (chris dollin) (2011-01-22)
Re: Intermediate forms (again?): worthwhile? cr88192@hotmail.com (BGB) (2011-01-22)
Re: Treating keywords as identifiers where possible robin51@dodo.com.au (robin) (2011-01-22)
Searching for a C/C++ Interpreter written in pure Java hier.mail.einwerfen@gmail.com (Michael Hielscher) (2011-01-20)
Re: are there implementation reasons for not providing a break stateme bc@freeuk.com (Bartc) (2011-01-20)
Algol 68 Genie version 2.1.1 - An Algol 68 implementation algol68g@xs4all.nl (Marcel van der Veer) (2011-01-20)
Re: Intermediate forms (again?): worthwhile? cr88192@hotmail.com (BGB) (2011-01-19)
how to parse this? n.oje.bar@gmail.com (nojb) (2011-01-19)
Re: error reporting, was language design implications genew@ocis.net (Gene Wirchenko) (2011-01-19)
Re: Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-19)
Re: Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-19)
Treating keywords as identifiers where possible anton@mips.complang.tuwien.ac.at (2011-01-19)
Re: are there implementation reasons for not providing a break stateme richard@cogsci.ed.ac.uk (2011-01-19)
Re: Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-19)
Re: Intermediate forms (again?): worthwhile? steshaw@gmail.com (Steven Shaw) (2011-01-19)
Re: Intermediate forms (again?): worthwhile? comp.compilers@inglorion.net (Robbert Haarman) (2011-01-19)
Re: language design implications for variant records in a pascal-like 9cn6w6402@sneakemail.com (Peter Canning) (2011-01-18)
Re: imperative-to-functional compiler martin@gkc.org.uk (Martin Ward) (2011-01-18)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-19)
Re: Language arcana [was PL/I arcana] robin51@dodo.com.au (robin) (2011-01-19)
Re: Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-18)
Re: are there implementation reasons for not providing a break stateme fusionfile@gmail.com (August Karlstrom) (2011-01-18)
Re: language design implications for variant records in a pascal-like mcr@wildcard.demon.co.uk (Martin Rodgers) (2011-01-18)
Re: are there implementation reasons for not providing a break stateme fusionfile@gmail.com (August Karlstrom) (2011-01-18)
Re: are there implementation reasons for not providing a break stateme richard@cogsci.ed.ac.uk (2011-01-18)
Re: imperative-to-functional compiler alain@dpt-info.u-strasbg.fr (Alain Ketterlin) (2011-01-18)
Re: imperative-to-functional compiler torbenm@diku.dk (2011-01-18)
Re: imperative-to-functional compiler pat@jantar.org (Patryk Zadarnowski) (2011-01-18)
imperative-to-functional compiler n.oje.bar@gmail.com (nojb) (2011-01-17)
Re: PL/I arcana, was language design implications for variant records compilers@is-not-my.name (2011-01-17)
Re: language design implications for variant records in a pascal-like genew@ocis.net (Gene Wirchenko) (2011-01-17)
Re: language design implications for variant records in a pascal-like dot@dotat.at (Tony Finch) (2011-01-17)
Re: language design implications for variant records in a pascal-like torbenm@diku.dk (2011-01-17)
Re: Abstract Interpretation vs DFA in Clang and GCC torbenm@diku.dk (2011-01-17)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-17)
Seed7 Release 2011-01-16 thomas.mertes@gmx.at (tm) (2011-01-16)
Re: language design implications for variant records in a pascal-like gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-16)
Re: are there implementation reasons for not providing a break stateme Pidgeot18@verizon.net (Joshua Cranmer) (2011-01-16)
Re: are there implementation reasons for not providing a break stateme bc@freeuk.com (BartC) (2011-01-16)
Re: language design implications for variant records in a pascal-like compilers@is-not-my.name (2011-01-16)
Compiler positions available for week ending January 16 compilers@iecc.com (comp.compilers) (2011-01-16)
Re: Intermediate forms (again?): worthwhile? gene.ressler@gmail.com (Gene) (2011-01-15)
ANN: Voodoo Compiler v0.7.0 Released comp.lang.misc@inglorion.net (Robbert Haarman) (2011-01-15)
Re: are there implementation reasons for not providing a break stateme anton@mips.complang.tuwien.ac.at (2011-01-15)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-15)
Re: language design implications for variant records in a pascal-like cfc@shell01.TheWorld.com (Chris F Clark) (2011-01-14)
Re: Lemon, fallback, and vacuous tokens. cfc@shell01.TheWorld.com (Chris F Clark) (2011-01-14)
Re: are there implementation reasons for not providing a break stateme fusionfile@gmail.com (August Karlstrom) (2011-01-14)
Re: are there implementation reasons for not providing a break stateme DrDiettrich1@aol.com (Hans-Peter Diettrich) (2011-01-14)
Re: language design implications for variant records in a pascal-like DrDiettrich1@aol.com (Hans-Peter Diettrich) (2011-01-14)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-14)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-14)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-14)
Re: language design implications for variant records in a pascal-like mcr@wildcard.demon.co.uk (Martin Rodgers) (2011-01-14)
Re: language design implications for variant records in a pascal-like compilers@is-not-my.name (2011-01-14)
Re: Intermediate forms (again?): worthwhile? comp.compilers@inglorion.net (Robbert Haarman) (2011-01-14)
Re: Intermediate forms (again?): worthwhile? cr88192@hotmail.com (BGB) (2011-01-14)
Intermediate forms (again?): worthwhile? nospam@myisp.net (Tony) (2011-01-13)
Re: language design implications for variant records in a pascal-like noitalmost@cox.net (noitalmost) (2011-01-13)
are there implementation reasons for not providing a break statement i noitalmost@cox.net (noitalmost) (2011-01-13)
Re: language design implications for variant records in a pascal-like compilers@is-not-my.name (2011-01-13)
Re: language design implications for variant records in a pascal-like gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-13)
Re: language design implications for variant records in a pascal-like gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-13)
Re: Looking for a real Fortran-66 compatible PC compiler (CP/M or DOS robin51@dodo.com.au (robin) (2011-01-13)
Re: language design implications for variant records in a pascal-like mcr@wildcard.demon.co.uk (Martin Rodgers) (2011-01-12)
Re: language design implications for variant records in a pascal-like DrDiettrich1@aol.com (Hans-Peter Diettrich) (2011-01-12)
Re: language design implications for variant records in a pascal-like martin@gkc.org.uk (Martin Ward) (2011-01-12)
Re: language design implications for variant records in a pascal-like martin@gkc.org.uk (Martin Ward) (2011-01-12)
Abstract Interpretation vs DFA in Clang and GCC ilikequoting@katamail.com (Jack Smith) (2011-01-10)
Re: language design implications for variant records in a pascal-like compilers@is-not-my.name (2011-01-10)
Re: language design implications for variant records in a pascal-like haberg-news@telia.com (Hans Aberg) (2011-01-10)
Re: language design implications for variant records in a pascal-like gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-10)
Re: language design implications for variant records in a pascal-like robin51@dodo.com.au (robin) (2011-01-10)
Re: language design implications for variant records in a pascal-like DrDiettrich1@aol.com (Hans-Peter Diettrich) (2011-01-08)
Parallelizing Induction Expression seimarao@gmail.com (Seima) (2011-01-07)
Re: language design implications for variant records in a pascal-like bobduff@shell01.TheWorld.com (Robert A Duff) (2011-01-06)
Re: language design implications for variant records in a pascal-like gneuner2@comcast.net (George Neuner) (2011-01-06)
Re: language design implications for variant records in a pascal-like gneuner2@comcast.net (George Neuner) (2011-01-06)
Re: language design implications for variant records in a pascal-like gneuner2@comcast.net (George Neuner) (2011-01-06)
Re: Making C compiler generate obfuscated code gneuner2@comcast.net (George Neuner) (2011-01-06)
Re: language design implications for variant records in a pascal-like gneuner2@comcast.net (George Neuner) (2011-01-06)
Re: language design implications for variant records in a pascal-like jm@bourguet.org (Jean-Marc Bourguet) (2011-01-05)
Re: Lemon, fallback, and vacuous tokens. rpw3@rpw3.org (2011-01-05)
Re: Making C compiler generate obfuscated code torbenm@diku.dk (2011-01-04)
Re: language design implications for variant records in a pascal-like torbenm@diku.dk (2011-01-04)
CFP: 2011 International Workshop on Multi-Core Computing Systems (MuCo pllana@par.univie.ac.at (Sabri Pllana) (2011-01-03)
Re: Lemon, fallback, and vacuous tokens. gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-03)
Re: Looking for a real Fortran-66 compatible PC compiler (CP/M or DOS gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-03)
Re: Integer division robin51@dodo.com.au (robin) (2011-01-03)
Re: language design implications for variant records in a pascal-like gene.ressler@gmail.com (Gene) (2011-01-02)
Seed7 Release 2011-01-02 thomas.mertes@gmx.at (tm) (2011-01-02)
Lemon, fallback, and vacuous tokens. darrencubitt@gmail.com (qarnos) (2011-01-02)
Re: Looking for a real Fortran-66 compatible PC compiler (CP/M or DOS gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-02)
Re: language design implications for variant records in a pascal-like gah@ugcs.caltech.edu (glen herrmannsfeldt) (2011-01-02)
Re: language design implications for variant records in a pascal-like noitalmost@cox.net (noitalmost) (2010-12-31)
Re: Looking for a real Fortran-66 compatible PC compiler (CP/M or DOS kargls@comcast.net (steve) (2010-12-31)
Re: language design implications for variant records in a pascal-like fw@deneb.enyo.de (Florian Weimer) (2010-12-31)
Re: language design implications for variant records in a pascal-like bobduff@shell01.TheWorld.com (Robert A Duff) (2010-12-31)
Re: language design implications for variant records in a pascal-like bobduff@shell01.TheWorld.com (Robert A Duff) (2010-12-31)
Twenty-five years of comp.compilers compilers-request@iecc.com (Comp.compilers) (2011-01-01)

| Previous month | Next month | Month index|

Return to the comp.compilers page.
Search the comp.compilers archives.