<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
>
<!-- MHonArc v2.6.10 -->
	<channel>
		<title>koneki-dev</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/maillist.html</link>
		<description>koneki-dev</description>
		<language>en-us</language>
		<pubDate>Wed, 02 May 2012 12:21:13 GMT</pubDate>
		<lastBuildDate>Wed, 02 May 2012 12:21:13 GMT</lastBuildDate>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		<generator>MHonArc RSS 2.0 RCFile</generator>
		<managingEditor>webmaster@eclipse.org (Webmaster)</managingEditor>
		<webMaster>webmaster@eclipse.org (Webmaster)</webMaster>
		<image>
			<title>koneki-dev</title>
			<url>http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg</url>
			<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/maillist.html</link>
		</image>
 

	<item>
		<title>Re: [koneki-dev] FW: mizar32 Lua board on sale</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00038.html</link>
		<description> </description>
		<content:encoded><![CDATA[<pre>Cool stuff, just miss a wireless shield :)

On Wed, May 2, 2012 at 10:33 AM, Benjamin Cab&#xE9; &lt;bcabe@xxxxxxxxxxxxxxxxxx&gt; wrote:
&gt; Hey guys,
&gt;
&gt; This little board looks really cool, and it is pretty cheap!
&gt; I think we should spend some cycles investigating what could be done to
&gt; support eLua in LDT...
&gt;
&gt; Benjamin.
&gt;
&gt; ________________________________________________________________________
&gt;
&gt;
&gt;
&gt;
&gt;
&gt; Le 02/05/12 00:36, &#xAB; Martin Guy &#xBB; &lt;martinwguy@xxxxxxxxx&gt; a &#xE9;crit :
&gt;
&gt;&gt;Hi
&gt;&gt; &#xA0;The Mizar32 board, the first commercial computer to come with Lua
&gt;&gt;(eLua) as its operating system, is now on sale at 4star.it
&gt;&gt;
&gt;&gt;Specs: 66Mhz AVR32 CPU, 32MB RAM, I2C, SPI, PWM, ADC, SD-card, USB
&gt;&gt;with UART, Ethernet, character LCD and VGA add-on modules.
&gt;&gt;
&gt;&gt;Web: <a  href="http://simplemachines.it/mizar32">http://simplemachines.it/mizar32</a>
&gt;&gt;Shop: <a  href="http://4star.it">http://4star.it</a> -&gt; mizar32
&gt;&gt;
&gt;&gt;best
&gt;&gt;
&gt;&gt; &#xA0; M
&gt;&gt;
&gt;&gt;
&gt;
&gt; _______________________________________________
&gt; koneki-dev mailing list
&gt; koneki-dev@xxxxxxxxxxx
&gt; <a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>

</pre>]]></content:encoded>
		<pubDate>Wed, 02 May 2012 12:13:14 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00038.html</guid>
		<author>jvermillard@xxxxxxx (Julien Vermillard)</author>
	</item>
	<item>
		<title>[koneki-dev] FW: mizar32 Lua board on sale</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00037.html</link>
		<description>Hey guys, This little board looks really cool, and it is pretty cheap! I think we should spend some cycles investigating what could be done to support eLua in LDT... Benjamin. ________________________________________________________________________ Le 02/0...</description>
		<content:encoded><![CDATA[<pre>Hey guys,

This little board looks really cool, and it is pretty cheap!
I think we should spend some cycles investigating what could be done to
support eLua in LDT...

Benjamin.

________________________________________________________________________





Le 02/05/12 00:36, &#xAB; Martin Guy &#xBB; &lt;martinwguy@xxxxxxxxx&gt; a &#xE9;crit :

&gt;Hi
&gt;  The Mizar32 board, the first commercial computer to come with Lua
&gt;(eLua) as its operating system, is now on sale at 4star.it
&gt;
&gt;Specs: 66Mhz AVR32 CPU, 32MB RAM, I2C, SPI, PWM, ADC, SD-card, USB
&gt;with UART, Ethernet, character LCD and VGA add-on modules.
&gt;
&gt;Web: <a  href="http://simplemachines.it/mizar32">http://simplemachines.it/mizar32</a>
&gt;Shop: <a  href="http://4star.it">http://4star.it</a> -&gt; mizar32
&gt;
&gt;best
&gt;
&gt;   M
&gt;
&gt;


</pre>]]></content:encoded>
		<pubDate>Wed, 02 May 2012 08:33:53 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00037.html</guid>
		<author>bcabe@xxxxxxx (Benjamin Cab&#xE9;)</author>
	</item>


	<item>
		<title>Re: [koneki-dev] LDT question</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00036.html</link>
		<description> </description>
		<content:encoded><![CDATA[<pre>Thank you. I will look at it.

On 2012-4-16, at &#xE4;&#xE5;9:19, Benjamin Cab&#xC3; wrote:

&gt; Hi,
&gt; 
&gt; A tentative fix is available on Github branch &quot;bug/376304&quot;
&gt; <a  href="https://github.com/SierraWireless/org.eclipse.koneki.ldt/tree/bug/376304">https://github.com/SierraWireless/org.eclipse.koneki.ldt/tree/bug/376304</a>
&gt; 
&gt; 
&gt; Benjamin.
&gt; 
&gt; 
&gt; 
&gt; 
&gt; Le 16/04/12 11:10, &#xC2; Benjamin Cab&#xC3; &#xC2; &lt;bcabe@xxxxxxxxxxxxxxxxxx&gt; a &#xC3;crit :
&gt; 
&gt;&gt; Hi Xu Cao,
&gt;&gt; 
&gt;&gt; Sorry for not having coming back to you earlier. The feature might a bit
&gt;&gt; tricky to implement since the AST currently lacks the information that
&gt;&gt; would allow a correct byte offset vs. char offset conversion.
&gt;&gt; I have a pending quick&amp;dirty hack for the error markers though that I will
&gt;&gt; push to a branch for you to have a look at, and maybe you'll find room for
&gt;&gt; improvement :-) I'll keep you posted when I will have done that.
&gt;&gt; 
&gt;&gt; Thanks so much for offering to work on the bug!
&gt;&gt; Benjamin.
&gt;&gt; 
&gt;&gt; ________________________________________________________________________
&gt;&gt; 
&gt;&gt; 
&gt;&gt; 
&gt;&gt; 
&gt;&gt; 
&gt;&gt; Le 16/04/12 11:04, &#xC2; cao.xu &#xC2; &lt;cao.xu@xxxxxxxxxx&gt; a &#xC3;crit :
&gt;&gt; 
&gt;&gt;&gt; Hi,
&gt;&gt;&gt; 
&gt;&gt;&gt; 	As the topic I sent in <a  href="http://www.eclipse.org/forums/index.php/t/320658/">http://www.eclipse.org/forums/index.php/t/320658/</a>
&gt;&gt;&gt; said, I was wondering if anyone could introduce how ldt implement the
&gt;&gt;&gt; feature Error Markers and which part of source code should I look at to
&gt;&gt;&gt; fixe the non-ascii characters problem.
&gt;&gt;&gt; 
&gt;&gt;&gt; 
&gt;&gt;&gt; BR
&gt;&gt;&gt; 
&gt;&gt;&gt; Xu Cao
&gt;&gt;&gt; _______________________________________________
&gt;&gt;&gt; koneki-dev mailing list
&gt;&gt;&gt; koneki-dev@xxxxxxxxxxx
&gt;&gt;&gt; <a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>
&gt;&gt;&gt; 
&gt;&gt; 
&gt;&gt; _______________________________________________
&gt;&gt; koneki-dev mailing list
&gt;&gt; koneki-dev@xxxxxxxxxxx
&gt;&gt; <a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>
&gt;&gt; 
&gt; 
&gt; _______________________________________________
&gt; koneki-dev mailing list
&gt; koneki-dev@xxxxxxxxxxx
&gt; <a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>


</pre>]]></content:encoded>
		<pubDate>Mon, 16 Apr 2012 15:26:40 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00036.html</guid>
		<author>cao.xu@xxxxxxx (cao.xu)</author>
	</item>
	<item>
		<title>Re: [koneki-dev] LDT question</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00035.html</link>
		<description>Hi, A tentative fix is available on Github branch &amp;quot;bug/376304&amp;quot; https://github.com/SierraWireless/org.eclipse.koneki.ldt/tree/bug/376304 Benjamin. Le 16/04/12 11:10, &amp;#xAB; Benjamin Cab&amp;#xE9; &amp;#xBB; &amp;lt;bcabe@xxxxxxxxxxxxxxxxxx&amp;gt; a &amp;#xE9;crit : </description>
		<content:encoded><![CDATA[<pre>Hi,

A tentative fix is available on Github branch &quot;bug/376304&quot;
<a  href="https://github.com/SierraWireless/org.eclipse.koneki.ldt/tree/bug/376304">https://github.com/SierraWireless/org.eclipse.koneki.ldt/tree/bug/376304</a>


Benjamin.




Le 16/04/12 11:10, &#xAB; Benjamin Cab&#xE9; &#xBB; &lt;bcabe@xxxxxxxxxxxxxxxxxx&gt; a &#xE9;crit :

&gt;Hi Xu Cao,
&gt;
&gt;Sorry for not having coming back to you earlier. The feature might a bit
&gt;tricky to implement since the AST currently lacks the information that
&gt;would allow a correct byte offset vs. char offset conversion.
&gt;I have a pending quick&amp;dirty hack for the error markers though that I will
&gt;push to a branch for you to have a look at, and maybe you'll find room for
&gt;improvement :-) I'll keep you posted when I will have done that.
&gt;
&gt;Thanks so much for offering to work on the bug!
&gt;Benjamin.
&gt;
&gt;________________________________________________________________________
&gt;
&gt;
&gt;
&gt;
&gt;
&gt;Le 16/04/12 11:04, &#xAB; cao.xu &#xBB; &lt;cao.xu@xxxxxxxxxx&gt; a &#xE9;crit :
&gt;
&gt;&gt;Hi,
&gt;&gt;
&gt;&gt;	As the topic I sent in <a  href="http://www.eclipse.org/forums/index.php/t/320658/">http://www.eclipse.org/forums/index.php/t/320658/</a>
&gt;&gt;said, I was wondering if anyone could introduce how ldt implement the
&gt;&gt;feature Error Markers and which part of source code should I look at to
&gt;&gt;fixe the non-ascii characters problem.
&gt;&gt;
&gt;&gt;
&gt;&gt;BR
&gt;&gt;
&gt;&gt;Xu Cao
&gt;&gt;_______________________________________________
&gt;&gt;koneki-dev mailing list
&gt;&gt;koneki-dev@xxxxxxxxxxx
&gt;&gt;<a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>
&gt;&gt;
&gt;
&gt;_______________________________________________
&gt;koneki-dev mailing list
&gt;koneki-dev@xxxxxxxxxxx
&gt;<a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>
&gt;


</pre>]]></content:encoded>
		<pubDate>Mon, 16 Apr 2012 13:19:13 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00035.html</guid>
		<author>bcabe@xxxxxxx (Benjamin Cab&#xE9;)</author>
	</item>
	<item>
		<title>Re: [koneki-dev] LDT question</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00034.html</link>
		<description>Hi Xu Cao, Sorry for not having coming back to you earlier. The feature might a bit tricky to implement since the AST currently lacks the information that would allow a correct byte offset vs. char offset conversion. I have a pending quick&amp;amp;dirty hack for t...</description>
		<content:encoded><![CDATA[<pre>Hi Xu Cao,

Sorry for not having coming back to you earlier. The feature might a bit
tricky to implement since the AST currently lacks the information that
would allow a correct byte offset vs. char offset conversion.
I have a pending quick&amp;dirty hack for the error markers though that I will
push to a branch for you to have a look at, and maybe you'll find room for
improvement :-) I'll keep you posted when I will have done that.

Thanks so much for offering to work on the bug!
Benjamin.

________________________________________________________________________





Le 16/04/12 11:04, &#xAB; cao.xu &#xBB; &lt;cao.xu@xxxxxxxxxx&gt; a &#xE9;crit :

&gt;Hi,
&gt;
&gt;	As the topic I sent in <a  href="http://www.eclipse.org/forums/index.php/t/320658/">http://www.eclipse.org/forums/index.php/t/320658/</a>
&gt;said, I was wondering if anyone could introduce how ldt implement the
&gt;feature Error Markers and which part of source code should I look at to
&gt;fixe the non-ascii characters problem.
&gt;
&gt;
&gt;BR
&gt;
&gt;Xu Cao
&gt;_______________________________________________
&gt;koneki-dev mailing list
&gt;koneki-dev@xxxxxxxxxxx
&gt;<a  href="http://dev.eclipse.org/mailman/listinfo/koneki-dev">http://dev.eclipse.org/mailman/listinfo/koneki-dev</a>
&gt;


</pre>]]></content:encoded>
		<pubDate>Mon, 16 Apr 2012 09:10:49 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00034.html</guid>
		<author>bcabe@xxxxxxx (Benjamin Cab&#xE9;)</author>
	</item>
	<item>
		<title>[koneki-dev] LDT question</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00033.html</link>
		<description>Hi, As the topic I sent in http://www.eclipse.org/forums/index.php/t/320658/ said, I was wondering if anyone could introduce how ldt implement the feature Error Markers and which part of source code should I look at to fixe the non-ascii characters problem...</description>
		<content:encoded><![CDATA[<pre>Hi,

	As the topic I sent in <a  href="http://www.eclipse.org/forums/index.php/t/320658/">http://www.eclipse.org/forums/index.php/t/320658/</a> said, I was wondering if anyone could introduce how ldt implement the feature Error Markers and which part of source code should I look at to fixe the non-ascii characters problem.


BR

Xu Cao
</pre>]]></content:encoded>
		<pubDate>Mon, 16 Apr 2012 09:05:02 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00033.html</guid>
		<author>cao.xu@xxxxxxx (cao.xu)</author>
	</item>


	<item>
		<title>[koneki-dev] LDT tutorials</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00032.html</link>
		<description>Just a quick note to let you know that I have started collecting LDT-related tutorials on the following wiki page: http://wiki.eclipse.org/Koneki/LDT/Tutorials Should you have any ideas of things to add, or know of existing tutorials already available on t...</description>
		<content:encoded><![CDATA[<pre>Just a quick note to let you know that I have started collecting
LDT-related tutorials on the following wiki page:
<a  href="http://wiki.eclipse.org/Koneki/LDT/Tutorials">http://wiki.eclipse.org/Koneki/LDT/Tutorials</a>

Should you have any ideas of things to add, or know of existing tutorials
already available on the Internet, please feel free to append them to the
list!

Cheers,
Benjamin.


</pre>]]></content:encoded>
		<pubDate>Tue, 03 Apr 2012 14:54:55 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00032.html</guid>
		<author>bcabe@xxxxxxx (Benjamin Cab&#xE9;)</author>
	</item>


	<item>
		<title>Re: [koneki-dev] The Record-block/Type-block</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00031.html</link>
		<description>Yes, it would be quite "challenging" to deduce it from C/C++ code - and likely highly error-prone.  That's why I asked would it be worth the trouble. :)At first I was going to say it would be nuts, but I've been looking at our API code and, for my company ...</description>
		<content:encoded><![CDATA[<div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:12pt"><div><span><br></span></div><div><span>Yes, it would be quite "challenging" to deduce it from C/C++ code - and likely highly error-prone. &nbsp;That's why I asked would it be worth the trouble. :)</span></div><div><span>At first I was going to say it would be nuts, but I've been looking at our API code and, for my company at least, it may be possible... for us. &nbsp;But we followed a (fairly) consistent pattern. &nbsp;In fact, so consistent a pattern I'm now debating whether we should have not written much C/C++ code to begin with, and instead done it as XML and generated the code through an XSLT script.</span></div><div><span><br></span></div><div><span>But anyway... yes having the doc languages be the same would be nice, but it's not that hard for folks to just write a script to convert their particular format into
 the Komeki LDT one. (Assuming they wrote their comments in some consistent format to begin with, like Doxygen format for example)</span></div><div><span><br></span></div><div><span>-hadriel</span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;">  <div style="font-size: 12pt; font-family: 'Courier New', courier, monaco, monospace, sans-serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1">  <b><span style="font-weight:bold;">From:</span></b> Fabien Fleutot &lt;fleutot+koneki@xxxxxxxxx&gt;<br> <b><span style="font-weight: bold;">To:</span></b> Hadriel Kaplan &lt;hadrielk@xxxxxxxxx&gt; <br><b><span style="font-weight: bold;">Cc:</span></b> General development dicussions for the Koneki project &lt;koneki-dev@xxxxxxxxxxx&gt; <br> <b><span style="font-weight:
 bold;">Sent:</span></b> Thursday, March 1, 2012 12:44 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [koneki-dev] The Record-block/Type-block<br> </font> </div> <br>
<div id="yiv1243819837"><br><br><div class="yiv1243819837gmail_quote">On Thu, Mar 1, 2012 at 5:53 PM, Hadriel Kaplan <span dir="ltr">&lt;<a rel="nofollow" ymailto="mailto:hadrielk@xxxxxxxxx" target="_blank" href="mailto:hadrielk@xxxxxxxxx">hadrielk@xxxxxxxxx</a>&gt;</span> wrote:<br><blockquote class="yiv1243819837gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="font-size: 12pt; font-family: 'Courier New', courier, monaco, monospace, sans-serif; "><div><span style="font-size:12pt;">As for the inferring of type information from code - assuming you mean from C/C++ code, is it really worth it?</span></div>
</div></blockquote><div><br></div><div>I was talking about Lua code. Parsing C++ code to guess what it does to an embedded scripting language would be... challenging. However, the doc languages in C++ and Lua comments sure should be the same.</div>
<div><br></div></div>
</div><br><br> </div> </div> </blockquote></div>   </div>]]></content:encoded>
		<pubDate>Fri, 02 Mar 2012 15:09:05 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00031.html</guid>
		<author>hadrielk@xxxxxxx (Hadriel Kaplan)</author>
	</item>


	<item>
		<title>Re: [koneki-dev] The Record-block/Type-block</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00030.html</link>
		<description>On Thu, Mar 1, 2012 at 5:53 PM, Hadriel Kaplan &amp;lt;hadrielk@xxxxxxxxx&amp;gt; wrote:I was talking about Lua code. Parsing C++ code to guess what it does to an embedded scripting language would be... challenging. However, the doc languages in C++ and Lua comments sur...</description>
		<content:encoded><![CDATA[<br><br><div class="gmail_quote">On Thu, Mar 1, 2012 at 5:53 PM, Hadriel Kaplan <span dir="ltr">&lt;<a href="mailto:hadrielk@xxxxxxxxx">hadrielk@xxxxxxxxx</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:12pt;font-family:Courier New,courier,monaco,monospace,sans-serif"><div><span style="font-size:12pt">As for the inferring of type information from code - assuming you mean from C/C++ code, is it really worth it?</span></div>
</div></blockquote><div><br></div><div>I was talking about Lua code. Parsing C++ code to guess what it does to an embedded scripting language would be... challenging. However, the doc languages in C++ and Lua comments sure should be the same.</div>
<div><br></div></div>
]]></content:encoded>
		<pubDate>Thu, 01 Mar 2012 17:44:05 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00030.html</guid>
		<author>fleutot+koneki@xxxxxxx (Fabien Fleutot)</author>
	</item>
	<item>
		<title>Re: [koneki-dev] The Record-block/Type-block</title>
		<link>http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00029.html</link>
		<description>Hi Fabien,I completely agree that it's not a high priority.  Just noting it as I'm trying to convert to using Koneki LDT. :)As for the inferring of type information from code - assuming you mean from C/C++ code, is it really worth it?  I mean the API devel...</description>
		<content:encoded><![CDATA[<div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:12pt"><div><span>Hi Fabien,</span></div><div><span>I completely agree that it's not a high priority. &nbsp;Just noting it as I'm trying to convert to using Koneki LDT. :)</span></div><div><span><br></span></div><div>As for the inferring of type information from code - assuming you mean from C/C++ code, is it really worth it? &nbsp;I mean the API developer will have to write the help/description text anyway, which is a big chunk of the comments to write. &nbsp;Although having said that, I agree it's usually the param/return types that are wrong in the comments/documentation, rather than the description, because the developers copy/paste the comments and change the description but forget to verify the types... hmmm, maybe it is worth
 it.</div><div><span><br></span></div><div><span>-hadriel</span></div><div><span><br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;">  <div style="font-size: 12pt; font-family: 'Courier New', courier, monaco, monospace, sans-serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1">  <b><span style="font-weight:bold;">From:</span></b> Fabien Fleutot &lt;fleutot@xxxxxxxxx&gt;<br> <b><span style="font-weight: bold;">To:</span></b> Hadriel Kaplan &lt;hadrielk@xxxxxxxxx&gt;; General development dicussions for the Koneki project &lt;koneki-dev@xxxxxxxxxxx&gt; <br> <b><span style="font-weight: bold;">Sent:</span></b> Thursday, March 1, 2012 4:47 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [koneki-dev] The Record-block/Type-block<br> </font> </div> <br>
<div id="yiv1095759568">On Thu, Mar 1, 2012 at 8:59 AM, Hadriel Kaplan <span dir="ltr">&lt;<a rel="nofollow" ymailto="mailto:hadrielk@xxxxxxxxx" target="_blank" href="mailto:hadrielk@xxxxxxxxx">hadrielk@xxxxxxxxx</a>&gt;</span> wrote:<br><div class="yiv1095759568gmail_quote"><blockquote class="yiv1095759568gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="font-size: 12pt; font-family: 'Courier New', courier, monaco, monospace, sans-serif; "><span><div style=""><span style="font-size:12pt;">But due to poor design [...] some APIs have many different enum lists/types they put in the same sub-table/global.</span></div>
</span></div></blockquote><div><br></div><div>Indeed, there are scary stuff on the wild :) However I'd argue that:</div><div><ul><li>given how ambitious the project is, at the very least supporting such poor designs shouldn't be a priority;</li>
<li>if writing correct code enables better IDE support, then a couple of people will start writing better code, and the world will be a slightly better place;</li><li>it would be very great if, in the future, a lot of typing information was inferred from the code rather than mandatorily written down in the comments. The messier the type system, the harder inference becomes. I'd rather leave the door open for inference than help people write unidiomatic code!</li>
</ul></div></div>
</div><br><br> </div> </div> </blockquote></div>   </div>]]></content:encoded>
		<pubDate>Thu, 01 Mar 2012 16:53:25 GMT</pubDate>
		<guid isPermaLink="true">http://dev.eclipse.org/mhonarc/lists/koneki-dev/msg00029.html</guid>
		<author>hadrielk@xxxxxxx (Hadriel Kaplan)</author>
	</item>

 
	</channel>
	</rss>
<!-- MHonArc v2.6.10 -->

