<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://groups.google.co.uk/group/comp.compilers</id>
  <title type="text">comp.compilers Google Group</title>
  <subtitle type="text">
  Compiler construction, theory, etc. (Moderated)
  </subtitle>
  <link href="/group/comp.compilers/feed/atom_v1_0_msgs.xml" rel="self" title="comp.compilers feed"/>
  <updated>2009-11-27T17:26:32Z</updated>
  <generator uri="http://groups.google.co.uk" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Robert A Duff</name>
  <email>bobd...@shell01.theworld.com</email>
  </author>
  <updated>2009-11-27T17:26:32Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/83381b0d6afd26ec/00559ece352ffe26?show_docid=00559ece352ffe26</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/83381b0d6afd26ec/00559ece352ffe26?show_docid=00559ece352ffe26"/>
  <title type="text">Re: parent pointers in AST nodes</title>
  <summary type="html" xml:space="preserve">
  I don&#39;t think it&#39;s common. &lt;br&gt; One compiler that keeps parent pointers in the tree is GNAT &lt;br&gt; (the gcc Ada compiler). &lt;br&gt; I find that code that follows parent pointers tends to be confusing. &lt;br&gt; Same reasons that global variables cause trouble. It&#39;s usually better &lt;br&gt; to pass information down the tree as parameters during the tree walk
  </summary>
  </entry>
  <entry>
  <author>
  <name>Martin B.</name>
  <email>0xcdcdc...@gmx.at</email>
  </author>
  <updated>2009-11-27T15:09:47Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/4b26d8b7b72178c3/15627922af00134e?show_docid=15627922af00134e</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/4b26d8b7b72178c3/15627922af00134e?show_docid=15627922af00134e"/>
  <title type="text">C++ - inlining of functions returning an unwindable object</title>
  <summary type="html" xml:space="preserve">
  Hi all. &lt;br&gt; Note that I&#39;ve first posted this to microsoft.public.vc.language and &lt;br&gt; after that to comp.lang.c++.moderated where I was told that someone on &lt;br&gt; comp.compilers may shed some light on this :-) &lt;br&gt; The Visual Studio compiler will never inline a funtion that returns an &lt;br&gt; unwindable object (e.g. std::string, CString, etc.)
  </summary>
  </entry>
  <entry>
  <author>
  <name>eliben</name>
  <email>eli...@gmail.com</email>
  </author>
  <updated>2009-11-27T13:32:11Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/83381b0d6afd26ec/7e57dbf9d1aa6ef3?show_docid=7e57dbf9d1aa6ef3</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/83381b0d6afd26ec/7e57dbf9d1aa6ef3?show_docid=7e57dbf9d1aa6ef3"/>
  <title type="text">parent pointers in AST nodes</title>
  <summary type="html" xml:space="preserve">
  Hello, &lt;br&gt; When implementing an AST for some language, each AST node typically &lt;br&gt; holds information about the language construct it represents and &lt;br&gt; pointers to children nodes (such as a binary op node pointing to its &lt;br&gt; left-hand and right-hand operands). &lt;br&gt; Is it common / useful to supply a pointer to the node&#39;s parent as
  </summary>
  </entry>
  <entry>
  <author>
  <name>Rob Economopoulos</name>
  <email>g...@ecs.soton.ac.uk</email>
  </author>
  <updated>2009-11-25T12:10:33Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/735e0cc5b17c5a97/e994bb15b4d4004f?show_docid=e994bb15b4d4004f</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/735e0cc5b17c5a97/e994bb15b4d4004f?show_docid=e994bb15b4d4004f"/>
  <title type="text">GPCE&#39;10 First Call for Papers (Eindhoven NL, Oct 10)</title>
  <summary type="html" xml:space="preserve">
  ------------------------------ ------------------------------ ------------ &lt;br&gt; CALL FOR PAPERS &lt;br&gt; Ninth International Conference on &lt;br&gt; Generative Programming and Component Engineering &lt;br&gt; (GPCE 2010) &lt;br&gt; October 10-13, 2010 &lt;br&gt; Eindhoven, The Netherlands
  </summary>
  </entry>
  <entry>
  <author>
  <name>comp.compilers</name>
  <email>compil...@iecc.com</email>
  </author>
  <updated>2009-11-22T09:00:07Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/066c900a20caea20/c17a7f3067d38894?show_docid=c17a7f3067d38894</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/066c900a20caea20/c17a7f3067d38894?show_docid=c17a7f3067d38894"/>
  <title type="text">Compiler positions available for week ending November 22</title>
  <summary type="html" xml:space="preserve">
  This is a digest of ``help wanted&#39;&#39; and ``position available&#39;&#39; messages &lt;br&gt; received at comp.compilers during the preceding week. Messages must &lt;br&gt; advertise a position having something to do with compilers and must also &lt;br&gt; conform to the guidelines periodically posted in misc.jobs.offered. &lt;br&gt; Positions that remain open may be re-advertised once a month. To respond
  </summary>
  </entry>
  <entry>
  <author>
  <name>Andrew Tomazos</name>
  <email>and...@tomazos.com</email>
  </author>
  <updated>2009-11-22T00:57:01Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/f70cc1db4ba19375/5a6366a17acd5954?show_docid=5a6366a17acd5954</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/f70cc1db4ba19375/5a6366a17acd5954?show_docid=5a6366a17acd5954"/>
  <title type="text">Re: compiling locks/ monitors</title>
  <summary type="html" xml:space="preserve">
  In the Windows API there are CriticalSection objects: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://msdn.microsoft.com/en-us/library/ms682530%28VS.85%29.aspx&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; and Mutex objects: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://msdn.microsoft.com/en-us/library/ms684266%28VS.85%29.aspx&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Under the POSIX API (implemented by NPTL under Linux) there are &lt;br&gt; mutexs: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;https://computing.llnl.gov/tutorials/pthreads/#MutexOverview&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Detlef Meyer-Eltz</name>
  <email>meyer-e...@t-online.de</email>
  </author>
  <updated>2009-11-19T12:55:46Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/e9e99ee34c012fa6/399e439c5e86bfbb?show_docid=399e439c5e86bfbb</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/e9e99ee34c012fa6/399e439c5e86bfbb?show_docid=399e439c5e86bfbb"/>
  <title type="text">Converter from Object-Pascal (Delphi) to C++</title>
  <summary type="html" xml:space="preserve">
  The program Delphi2Cpp just has been released at: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.texttransformer.com/Delphi2Cpp_en.html&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; Delphi2Cpp helps to convert Delphi source code to C++. The program &lt;br&gt; saves all simple purely mechanical syntactical substitutions and &lt;br&gt; rearrangements of the code in which the largest portion of the &lt;br&gt; translation consists. A lot of more complex translation steps are
  </summary>
  </entry>
  <entry>
  <author>
  <name>Arnaud Gotlieb</name>
  <email>arnaud.gotl...@irisa.fr</email>
  </author>
  <updated>2009-11-17T09:04:03Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/e7864674b338da01/49d685fa6ea08a56?show_docid=49d685fa6ea08a56</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/e7864674b338da01/49d685fa6ea08a56?show_docid=49d685fa6ea08a56"/>
  <title type="text">CFP: 2nd Workshop on Constraints in Software Testing, Verification and Analysis (Paris, Apr 10)</title>
  <summary type="html" xml:space="preserve">
  CALL FOR PAPERS &lt;br&gt; CSTVA&#39;10 &lt;br&gt; 2nd Workshop on &lt;br&gt; Constraints in Software Testing, Verification and Analysis &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.st.cs.uni-saarland.de/cstva10/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; April 10, 2010 &lt;br&gt; Paris, France &lt;br&gt; Held in conjunction with the International Conference on &lt;br&gt; Software Testing, Verification and Validation, ICST 2010, &lt;br&gt; April 6-10, 2010:
  </summary>
  </entry>
  <entry>
  <author>
  <name>Antonio Cunei</name>
  <email>scaladays2...@cunei.com</email>
  </author>
  <updated>2009-11-18T11:50:31Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/d3cc07f4466f58e0/ca00debe13af861a?show_docid=ca00debe13af861a</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/d3cc07f4466f58e0/ca00debe13af861a?show_docid=ca00debe13af861a"/>
  <title type="text">The First Scala Workshop - Scala Days 2010 (Lausanne CH, Apr 10)</title>
  <summary type="html" xml:space="preserve">
  The First Scala Workshop &lt;br&gt; ======================== &lt;br&gt; Call for Papers &lt;br&gt; --------------- &lt;br&gt; Scala is a general purpose programming language designed to express &lt;br&gt; common programming patterns in a concise, elegant, and type-safe &lt;br&gt; way. It smoothly integrates features of object-oriented and &lt;br&gt; functional languages. &lt;br&gt; This workshop is a forum for researchers and practitioners to share
  </summary>
  </entry>
  <entry>
  <author>
  <name>Hans Aberg</name>
  <email>haberg_20080...@math.su.se</email>
  </author>
  <updated>2009-11-17T09:16:59Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/db8cf9172ca0ac1a/4b36240daa7ded0d?show_docid=4b36240daa7ded0d</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/db8cf9172ca0ac1a/4b36240daa7ded0d?show_docid=4b36240daa7ded0d"/>
  <title type="text">Re: Switch statement code generation</title>
  <summary type="html" xml:space="preserve">
  The Wikipedia perfect hash function page says this is the definition of &lt;br&gt; a perfect hash function. It is called a minimal perfect function if the &lt;br&gt; image is an interval. &lt;br&gt; It also mentions some libraries implementing minimal perfect hash functions: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://cmph.sourceforge.net/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://sux4j.dsi.unimi.it/&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Quinn Tyler Jackson</name>
  <email>quinn_jackson2...@yahoo.ca</email>
  </author>
  <updated>2009-11-17T05:59:54Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/17250e0b871eb1be/33014f429240bcae?show_docid=33014f429240bcae</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/17250e0b871eb1be/33014f429240bcae?show_docid=33014f429240bcae"/>
  <title type="text">Meta-S and The Grammar Forge</title>
  <summary type="html" xml:space="preserve">
  Hello! &lt;br&gt; In another forum, I noticed what appeared to be some possible &lt;br&gt; confusion as to the status of the Meta-S parser and The Grammar Forge. &lt;br&gt; The Meta-S technology and The Grammar Forge are indeed alive and well &lt;br&gt; (now in version 8.0), and are the subject of daily research and &lt;br&gt; development. Commercial as well as academic/research licensing are
  </summary>
  </entry>
  <entry>
  <author>
  <name>Pertti Kellomaki</name>
  <email>pertti.kellom...@tut.fi</email>
  </author>
  <updated>2009-11-16T07:45:39Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/db8cf9172ca0ac1a/6e3e299db2b3fd82?show_docid=6e3e299db2b3fd82</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/db8cf9172ca0ac1a/6e3e299db2b3fd82?show_docid=6e3e299db2b3fd82"/>
  <title type="text">Re: Switch statement code generation</title>
  <summary type="html" xml:space="preserve">
  John wrote: &lt;br&gt; Is there a technical term for such slightly imperfect hashes? &lt;br&gt; Mathematically it would be an injection I suppose, but I have &lt;br&gt; not seen that term used in connection with hashing.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Chris F Clark</name>
  <email>c...@shell01.theworld.com</email>
  </author>
  <updated>2009-11-16T04:39:25Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/647b842a62af940b/4d1f195f6382648e?show_docid=4d1f195f6382648e</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/647b842a62af940b/4d1f195f6382648e?show_docid=4d1f195f6382648e"/>
  <title type="text">Re: Parsers, grammars and BNF</title>
  <summary type="html" xml:space="preserve">
  It depends on what sort of advice you are looking for on writing BNF. &lt;br&gt; If you wariting plain BNF (not EBNF--i.e. no regexes), there are some &lt;br&gt; basic structures that are used and not many variations to worry about. &lt;br&gt; For example, if you want an optional A (sometime written A-opt or in &lt;br&gt; EBMF A?), you write a rule like:
  </summary>
  </entry>
  <entry>
  <author>
  <name>Chris F Clark</name>
  <email>c...@shell01.theworld.com</email>
  </author>
  <updated>2009-11-16T04:11:00Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/caae6ac85dd19944/b79ff76a8ce9a6e6?show_docid=b79ff76a8ce9a6e6</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/caae6ac85dd19944/b79ff76a8ce9a6e6?show_docid=b79ff76a8ce9a6e6"/>
  <title type="text">Re: Switch statement code generation</title>
  <summary type="html" xml:space="preserve">
  Hashes versus Tries: &lt;br&gt; We&#39;ve done a fair amount of experimentation on hashing verus trie &lt;br&gt; building in our latest hardware design. As about 4 characters, hashes &lt;br&gt; start to win. And, in our case, we can fit either in 1st level cache, &lt;br&gt; that we can lock against spills, so cache misses aren&#39;t a penalty, &lt;br&gt; which tend to make hashing an even better choice. Now, actual hardware
  </summary>
  </entry>
  <entry>
  <author>
  <name>glen herrmannsfeldt</name>
  <email>g...@ugcs.caltech.edu</email>
  </author>
  <updated>2009-11-16T00:15:33Z</updated>
  <id>http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/647b842a62af940b/922d177152d32379?show_docid=922d177152d32379</id>
  <link href="http://groups.google.co.uk/group/comp.compilers/browse_thread/thread/647b842a62af940b/922d177152d32379?show_docid=922d177152d32379"/>
  <title type="text">Re: Parsers, grammars and BNF</title>
  <summary type="html" xml:space="preserve">
  Many years ago (1977) I worked on a macro-processor called STEP. &lt;br&gt; Well, someone had written it, declared it finished, and then left. &lt;br&gt; I got to test it out, try some simple and not so simple problems, &lt;br&gt; and make some improvements. &lt;br&gt; As far as I know, the manual still exists but the program itself &lt;br&gt; does not. It was written in IBM Fortran IV, or maybe standard
  </summary>
  </entry>
</feed>
