tag:blogger.com,1999:blog-2660857613420302960.post1910055316266637691..comments2024-03-01T03:28:13.083-05:00Comments on The Official Eclipse EDT Team Blog: What's cooking in the EDT kitchen? - November 13Xegl Teamhttp://www.blogger.com/profile/16028710936748007825noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-2660857613420302960.post-49304977304254008392012-11-22T07:36:04.062-05:002012-11-22T07:36:04.062-05:00The post is talking about what is cooking in the K...The post is talking about what is cooking in the Kitchen in November. Read t know more<br /><a href="http://www.superteams.com.au/corporate-master-chef" rel="nofollow">Cooking team building</a><br /><a href="http://www.superteams.com.au/" rel="nofollow">Team Activities</a>Daniel Anthonyhttps://www.blogger.com/profile/02608472916563989268noreply@blogger.comtag:blogger.com,1999:blog-2660857613420302960.post-77808180375534012962012-11-14T13:04:37.916-05:002012-11-14T13:04:37.916-05:00Nah. It was just a conversation starter. I know th...Nah. It was just a conversation starter. I know the chances of such a thing making it into EGL fall between slim and none.<br /><br />--Dan<br />Danhttps://www.blogger.com/profile/04754348598098569863noreply@blogger.comtag:blogger.com,1999:blog-2660857613420302960.post-89070171441148982742012-11-14T10:18:59.095-05:002012-11-14T10:18:59.095-05:00Hi Dan. Thanks for the idea. The best way to mak...Hi Dan. Thanks for the idea. The best way to make suggestions like this is to open a bug against EDT with severity=enhancement and component=Language. Or use this handy URL https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EDT;bug_severity=enhancement;component=LanguageMatt Heitzhttps://www.blogger.com/profile/03044786937973887004noreply@blogger.comtag:blogger.com,1999:blog-2660857613420302960.post-21000646496336531632012-11-13T17:59:51.121-05:002012-11-13T17:59:51.121-05:00"I doubt they'll be the only language enh..."I doubt they'll be the only language enhancements we add."<br /><br />One of the things that RPG'ers really appreciate about their language is an ENDyyy statement that explicitly marries up with its partner. (Optionally, you can use a generic END statement just as we do in EGL.) What a terrific addition to EGL this would be!<br /><br />Examples from RPG:<br /><br />ENDCS<br /> End a CASxx group <br /><br />ENDDO<br /> End a DO, DOU, DOUxx, DOW, or DOWxx group <br /><br />ENDFOR<br /> End a FOR group <br /><br />ENDIF<br /> End an IF or IFxx group <br /><br />ENDMON<br /> End a MONITOR group <br /><br />ENDSL<br /> End a SELECT group <br /><br />And again, an "END" can be used in place of any of these for those who prefer it.<br /><br />In EGL you might (optionally) use:<br />end-case<br />end-while<br />end-if<br />end-for<br />end-try<br />end-function<br />end-delegate<br />end-record<br />end-library<br />end-handler<br />end-service<br />end-program<br /><br />..and so on.<br /><br />Yes, we nest our code in free-format RPG but it is still all about clarity and an ENDyyy statement that indicates its partner adds clarity.<br /><br />This is an area where -- for those of us who use both languages daily -- the syntax of RPG is clearly superior to EGL.<br /><br />It wouldn't make much difference for the outer-most wrappers (such as "handler" or "service") but it makes a huge readability difference for the "if", "for", "case", "while", "try". I challenge you to take some business logic in EGL and look at it both ways. Which one is easier to follow?<br /><br />--DanDanhttps://www.blogger.com/profile/04754348598098569863noreply@blogger.com