<?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.com/group/comp.lang.eiffel</id>
  <title type="text">comp.lang.eiffel Google Group</title>
  <subtitle type="text">
  The object-oriented Eiffel language.
  </subtitle>
  <link href="/group/comp.lang.eiffel/feed/atom_v1_0_msgs.xml" rel="self" title="comp.lang.eiffel feed"/>
  <updated>2008-08-30T02:45:01Z</updated>
  <generator uri="http://groups.google.com" version="1.99">Google Groups</generator>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-30T02:45:01Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/732dbad3df7aa047/3256e084ce256445?show_docid=3256e084ce256445</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/732dbad3df7aa047/3256e084ce256445?show_docid=3256e084ce256445"/>
  <title type="text">The Eiffel Compiler tecomp version 0.3 released</title>
  <summary type="html" xml:space="preserve">
  Version 0.3 of &amp;quot;The Eiffel Compiler&amp;quot; tecomp has been released. &lt;br&gt; The Eiffel Compiler works on Unix and Windows environments. &lt;br&gt; Tecomp is a command line compiler for the Eiffel language. It &lt;br&gt; compiles &lt;br&gt; the Eiffel source code into an internal representation and executes &lt;br&gt; it &lt;br&gt; in its virtual machine. In its simplest configuration it works like
  </summary>
  </entry>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-30T02:41:53Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/732dbad3df7aa047/bdff349ddef0237d?show_docid=bdff349ddef0237d</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/732dbad3df7aa047/bdff349ddef0237d?show_docid=bdff349ddef0237d"/>
  <title type="text">The Eiffel Compiler tecomp version 0.3 released</title>
  <summary type="html" xml:space="preserve">
  Version 0.3 of &amp;quot;The Eiffel Compiler&amp;quot; tecomp has been released. &lt;br&gt; The Eiffel Compiler works on Unix and Windows environments. &lt;br&gt; Tecomp is a command line compiler for the Eiffel language. It &lt;br&gt; compiles &lt;br&gt; the Eiffel source code into an internal representation and executes &lt;br&gt; it &lt;br&gt; in its virtual machine. In its simplest configuration it works like
  </summary>
  </entry>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-18T12:53:08Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/b652e4bff20f199a?show_docid=b652e4bff20f199a</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/b652e4bff20f199a?show_docid=b652e4bff20f199a"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  On Aug 18, 6:38 am, Ulrich Windl &amp;lt;Ulrich.Wi...@RZ.Uni-Regensbur g.DE&amp;gt; &lt;br&gt; wrote: &lt;br&gt; clearly not like BASIC. Under the hood it is compilation. Tecomp has a &lt;br&gt; parser which converts the Eiffel code into some intermediate &lt;br&gt; representation (a more compact form than ASTs) and then a validator, &lt;br&gt; which validates the code. So if you write big programs in Eiffel, you
  </summary>
  </entry>
  <entry>
  <author>
  <name>Ulrich Windl</name>
  <email>ulrich.wi...@rz.uni-regensburg.de</email>
  </author>
  <updated>2008-08-18T11:38:46Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/d866b50ad4489e10?show_docid=d866b50ad4489e10</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/d866b50ad4489e10?show_docid=d866b50ad4489e10"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  Can you elaborate on &amp;quot;immediately&amp;quot;?: You mean once the system has been &lt;br&gt; compiled into some intermediate code. I doubt you can run Eiffel code like &lt;br&gt; BASIC... ;-)
  </summary>
  </entry>
  <entry>
  <author>
  <name>Mutual Assets</name>
  <email>comcovm...@yahoo.se</email>
  </author>
  <updated>2008-08-18T08:19:42Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/384548b4cef986f1/dc6560268301894d?show_docid=dc6560268301894d</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/384548b4cef986f1/dc6560268301894d?show_docid=dc6560268301894d"/>
  <title type="text">Hollywood NetBook™ Thought the $300 million compendium....</title>
  <summary type="html" xml:space="preserve">
  Filmproducer / Filmdirector &lt;br&gt; Har ni nagot gig at oss...? &lt;br&gt; Vi söker konsultuppdrag/konsultering inom filmproduktion. &lt;br&gt; Vänligen &lt;br&gt; Mr Roger K. Olsson &lt;br&gt; Int: +46 (0) 705474830 &lt;br&gt; Giuen Holding Ltd. Trade Confederation 2008-08-20 to financial &lt;br&gt; merchandise and entrepreneurial succeeding seeks agreement to new &lt;br&gt; easy
  </summary>
  </entry>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-17T23:47:56Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/52535b8c364cd3d2?show_docid=52535b8c364cd3d2</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/52535b8c364cd3d2?show_docid=52535b8c364cd3d2"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  Not necessarily. I can firstly parse the whole system (i.e. convert &lt;br&gt; the Eiffel source code to some internal representation), then start at &lt;br&gt; the root procedure and validate (i.e. semantic analysis) only used &lt;br&gt; features. Thats a kind of &amp;quot;lazy mode&amp;quot;. I.e. you do not touch &amp;quot;dead &lt;br&gt; code&amp;quot;. As far as I know, SmartEiffel works in that manner.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-17T16:13:46Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/927e28de9fd42e6e/0e442d79f8969c5d?show_docid=0e442d79f8969c5d</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/927e28de9fd42e6e/0e442d79f8969c5d?show_docid=0e442d79f8969c5d"/>
  <title type="text">Re: The Eiffel Compiler tecomp 0.2 released</title>
  <summary type="html" xml:space="preserve">
  The main question for me is: What is the most appropriate granularity &lt;br&gt; for doing C to native compilation? The feature, the class, the type, &lt;br&gt; the cluster or ...? &lt;br&gt; The best incremental strategy can be reached if you use the feature as &lt;br&gt; its finest granularity. So if you change a feature, you need to &lt;br&gt; recompile only the used features which depend on that feature. Ideally
  </summary>
  </entry>
  <entry>
  <author>
  <email>scholz.lot...@gmail.com</email>
  </author>
  <updated>2008-08-16T22:53:36Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/5ebb0922eaac9f83?show_docid=5ebb0922eaac9f83</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/5ebb0922eaac9f83?show_docid=5ebb0922eaac9f83"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  Yes, as i said maybe i did it wrong. There are multiple &lt;br&gt; ways you can do it. The easiest is just to duplicate AST &lt;br&gt; (abstract syntax tree) and then you don&#39;t need any special &lt;br&gt; code for generics. It works fine but as i said it does use &lt;br&gt; a lot of memory. &lt;br&gt; If you the substitution on demand and just have to check
  </summary>
  </entry>
  <entry>
  <author>
  <email>scholz.lot...@gmail.com</email>
  </author>
  <updated>2008-08-16T22:39:57Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/927e28de9fd42e6e/764fca74235e69cb?show_docid=764fca74235e69cb</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/927e28de9fd42e6e/764fca74235e69cb?show_docid=764fca74235e69cb"/>
  <title type="text">Re: The Eiffel Compiler tecomp 0.2 released</title>
  <summary type="html" xml:space="preserve">
  Well i read the page, the manual and the examples. &lt;br&gt; Installing the system didn&#39;t work for me. Neither 2.2 nor 2.3 &lt;br&gt; worked out of the box on my WinXP 64/MSVC 8.0 system. &lt;br&gt; And i didn&#39;t spend time into resolving the problem. &lt;br&gt; But of course you can use gcc. The main problem with eiffels &lt;br&gt; full system analysis and compiling to C strategy is not solved
  </summary>
  </entry>
  <entry>
  <author>
  <email>lawrence.quad...@gmail.com</email>
  </author>
  <updated>2008-08-14T22:15:59Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/68af4f0e512d73bc/b76b755b295ac5ad?show_docid=b76b755b295ac5ad</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/68af4f0e512d73bc/b76b755b295ac5ad?show_docid=b76b755b295ac5ad"/>
  <title type="text">comp.lang.eiffel licence</title>
  <summary type="html" xml:space="preserve">
  &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://carrier.googlebong.com&quot;&gt;[link]&lt;/a&gt;
  </summary>
  </entry>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-14T12:44:33Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/569e2d02d9dd0408?show_docid=569e2d02d9dd0408</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/569e2d02d9dd0408?show_docid=569e2d02d9dd0408"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  Hello Lothar, &lt;br&gt; I don&#39;t have the problem you mentioned. Tecomp only has one internal &lt;br&gt; representation per class. For each type I have some lean additional &lt;br&gt; information (e.g. describing layout information for the actual &lt;br&gt; generics). Also the routines have just some lean additional &lt;br&gt; information related to the actual generics. With that the virtual
  </summary>
  </entry>
  <entry>
  <author>
  <email>scholz.lot...@gmail.com</email>
  </author>
  <updated>2008-08-13T12:52:59Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/59ea7c5eac3ed8c2?show_docid=59ea7c5eac3ed8c2</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/59ea7c5eac3ed8c2?show_docid=59ea7c5eac3ed8c2"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  Yes. Maybe i used a wrong algorithm but it is still the only thing &lt;br&gt; not working well for my system. If you don&#39;t want to use excessive &lt;br&gt; O(n*n) memory like gobos gec (which already make people think about &lt;br&gt; using a 64bit system) then you need a clever algorithm which is not &lt;br&gt; simply duplicating complete ASTs.
  </summary>
  </entry>
  <entry>
  <author>
  <email>peter_gum...@hotmail.com</email>
  </author>
  <updated>2008-08-13T11:08:30Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/64f7a27307162022?show_docid=64f7a27307162022</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/64f7a27307162022?show_docid=64f7a27307162022"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  What do you mean by the &amp;quot;template system&amp;quot;, Lothar? Do you mean &lt;br&gt; generics? &lt;br&gt; -- Peter
  </summary>
  </entry>
  <entry>
  <author>
  <email>scholz.lot...@gmail.com</email>
  </author>
  <updated>2008-08-12T12:21:06Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/ae2d022fb6625287?show_docid=ae2d022fb6625287</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/ae2d022fb6625287?show_docid=ae2d022fb6625287"/>
  <title type="text">Re: Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  A little hint from me after writting my own eiffel compiler (not &lt;br&gt; finished). &lt;br&gt; The hardest thing was the template system, you should focus on this &lt;br&gt; first. &lt;br&gt; Object Orientation, even multiple inheritence is much easier to &lt;br&gt; implement. &lt;br&gt; In both phases: semantik validation and code generation. &lt;br&gt; Once you have done this i will give it a try.
  </summary>
  </entry>
  <entry>
  <author>
  <name>Helmut</name>
  <email>helmut.bra...@gmx.net</email>
  </author>
  <updated>2008-08-11T23:14:24Z</updated>
  <id>http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/1f3b8299a294d112?show_docid=1f3b8299a294d112</id>
  <link href="http://groups.google.com/group/comp.lang.eiffel/browse_thread/thread/a5c21d367224001c/1f3b8299a294d112?show_docid=1f3b8299a294d112"/>
  <title type="text">Eiffel interpreter available</title>
  <summary type="html" xml:space="preserve">
  Most of Eiffel compilers act like usual compilers. They compile to C &lt;br&gt; and then to native or directly to native machine code. &lt;br&gt; The Eiffel Compiler tecomp has chosen a different strategy. It its &lt;br&gt; simplest configuration it works like an interpreter. Just feed the &lt;br&gt; Eiffel source code and you get it executed immediately (see
  </summary>
  </entry>
</feed>
