<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Activity for Dialect</title><link href="https://sourceforge.net/p/dialect/activity/" rel="alternate"/><id>https://sourceforge.net/p/dialect/activity/</id><updated>2023-04-14T19:37:17.781000Z</updated><subtitle>Recent activity for Dialect</subtitle><entry><title>sbettini modified a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/4065e9c17a/?limit=25#dc60" rel="alternate"/><published>2023-04-14T19:37:17.781000Z</published><updated>2023-04-14T19:37:17.781000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/4065e9c17a/?limit=25#dc60</id><summary type="html">in case someone would be still interested, after playing a day with debugger I think that this serious bug now is solved. In order to have a correct evaluation tokAnd and tokOr need to start/end new sub-expressions, so in DialectInterp.cpp you have to remove management from FirstRelational() and SecondRelational() putting this in _Expression(): case tokAnd: ++m_Token; if (! result-&gt;Boolean()) return true; // shortcircuit and if (!_Expression(&amp;temp)) return false; *result = *result &amp;&amp; temp; return...</summary></entry><entry><title>sbettini modified a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/4065e9c17a/?limit=25#dc60" rel="alternate"/><published>2023-04-14T17:37:27.196000Z</published><updated>2023-04-14T17:37:27.196000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/4065e9c17a/?limit=25#dc60</id><summary type="html">in case someone would be still interested, after playing a day with debugger I think that this serious bug now is solved. In order to have a correct evaluation tokAnd and tokOr need to start/end new sub-expressions, so in DialectInterp.cpp you have to remove management from FirstRelational() and SecondRelational() putting this in _Expression(): case tokAnd: ++m_Token; if (! result-&gt;Boolean()){ // shortcircuit and *result = false; return true; } if (!_Expression(&amp;temp)) return false; *result = *result...</summary></entry><entry><title>sbettini posted a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/4065e9c17a/?limit=25#dc60" rel="alternate"/><published>2023-04-14T16:55:02.005000Z</published><updated>2023-04-14T16:55:02.005000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/4065e9c17a/?limit=25#dc60</id><summary type="html">in case someone would be still interested, after playing a day with debugger I think that this serious bug now is solved. In order to have a correct evaluation tokAnd and tokOr need to start/end new sub-expressions, so in DialectInterp.cpp you have to remove management from FirstRelational() and SecondRelational() putting this in _Expression(): case tokAnd: ++m_Token; if (!_Expression(&amp;temp)) return false; *result = *result &amp;&amp; temp; return true; case tokOr: ++m_Token; if (!_Expression(&amp;temp)) return...</summary></entry><entry><title>sbettini posted a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/d1a295c7cb/?limit=25#33e2/5de0" rel="alternate"/><published>2023-04-07T23:59:36.417000Z</published><updated>2023-04-07T23:59:36.417000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/d1a295c7cb/?limit=25#33e2/5de0</id><summary type="html">I can perfectly understand George, thanks. What a shame be not completely self-sufficient to keep going this wonderful product. I learned C++ playing with your very brilliant source, and was (and still is!) a challenge and a joy. Many thanks again for your work Stefano</summary></entry><entry><title>sbettini posted a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/6bc9ea0012/?limit=25#5b66" rel="alternate"/><published>2023-04-07T23:43:22.173000Z</published><updated>2023-04-07T23:43:22.173000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/6bc9ea0012/?limit=25#5b66</id><summary type="html">Probably posting on TICKET section was not a good idea.... if 1 = 2 and 2 = 3 print true else print false endif ---&gt;true (BUG) if (1 = 2) and (2 = 3) print true else print false endif ---&gt;false (CORRECT) Unfortunately seem to be a major problem at parser level (_Expression() and descendant tree functions) not so simple to manage, at least for me. The parens workaround is a little annoing and break the elegance of the syntax, could someone check with some old version (pre 1.16) if the problem was...</summary></entry><entry><title>sbettini created ticket #8</title><link href="https://sourceforge.net/p/dialect/bugs/8/" rel="alternate"/><published>2023-04-07T23:36:55.299000Z</published><updated>2023-04-07T23:36:55.299000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/bugs/8/</id><summary type="html">BUG in parsing boolean expressions (if, while....)</summary></entry><entry><title>George Harth posted a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/d1a295c7cb/?limit=25#33e2" rel="alternate"/><published>2020-05-13T20:28:00.125000Z</published><updated>2020-05-13T20:28:00.125000Z</updated><author><name>George Harth</name><uri>https://sourceforge.net/u/georgeh/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/d1a295c7cb/?limit=25#33e2</id><summary type="html">Hey Stefano! Sorry for my very late reply. I only just saw this. It has been many, many years since I've looked at this code. I love the threading idea, but I couldn't even begin to make reasonable suggestions without spending a good deal of time refreshing my memory. Cheers... George</summary></entry><entry><title>sbettini posted a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/d1a295c7cb/?limit=25#7df1" rel="alternate"/><published>2019-04-15T16:07:32.647000Z</published><updated>2019-04-15T16:07:32.647000Z</updated><author><name>sbettini</name><uri>https://sourceforge.net/u/sbettini/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/d1a295c7cb/?limit=25#7df1</id><summary type="html">I'm still working on this beautiful software, implementing some of less developed area. Now I would like to work on threading, and I wonder what was the original idea behind the partial work on cvalue. Being the stack and the token pointer unique inside the interpreter a simple statement "do_async" that run the interpret in a new thread could not be enough, I think that the threaded code must have at least his own copy of the current stack... Maybe a complete copy of the current CDialectInterp instance?...</summary></entry><entry><title>Milville posted a comment on discussion Help</title><link href="https://sourceforge.net/p/dialect/discussion/137830/thread/805ff0d3/?limit=25#d061" rel="alternate"/><published>2015-02-19T14:04:29.206000Z</published><updated>2015-02-19T14:04:29.206000Z</updated><author><name>Milville</name><uri>https://sourceforge.net/u/jminabla/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137830/thread/805ff0d3/?limit=25#d061</id><summary type="html">Unbelievable: I was expecting to be the last one in the world to use Dialect... In...</summary></entry><entry><title>Mr.NonObservant modified a comment on discussion Help</title><link href="https://sourceforge.net/p/dialect/discussion/137830/thread/805ff0d3/?limit=25#d8b5" rel="alternate"/><published>2015-02-18T16:59:29.258000Z</published><updated>2015-02-18T16:59:29.258000Z</updated><author><name>Mr.NonObservant</name><uri>https://sourceforge.net/u/mrnonobservant/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137830/thread/805ff0d3/?limit=25#d8b5</id><summary type="html">Guilect GUI Editor and Sample Source http://www.mediafire.com/download/fph712tls09p3qw/Guilect16.zip...</summary></entry><entry><title>Mr.NonObservant posted a comment on discussion Help</title><link href="https://sourceforge.net/p/dialect/discussion/137830/thread/805ff0d3/?limit=25#d8b5" rel="alternate"/><published>2015-02-18T16:58:46.813000Z</published><updated>2015-02-18T16:58:46.813000Z</updated><author><name>Mr.NonObservant</name><uri>https://sourceforge.net/u/mrnonobservant/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137830/thread/805ff0d3/?limit=25#d8b5</id><summary type="html">Guilect GUI Editor and Sample Source http://www.mediafire.com/download/fph712tls09p3qw/Guilect16.zip...</summary></entry><entry><title>Mr.NonObservant posted a comment on discussion Open Discussion</title><link href="https://sourceforge.net/p/dialect/discussion/137829/thread/b24ca2d8/?limit=25#47a0" rel="alternate"/><published>2015-02-18T16:49:48.608000Z</published><updated>2015-02-18T16:49:48.608000Z</updated><author><name>Mr.NonObservant</name><uri>https://sourceforge.net/u/mrnonobservant/profile/</uri></author><id>https://sourceforge.net/p/dialect/discussion/137829/thread/b24ca2d8/?limit=25#47a0</id><summary type="html">I got GUILECT and a bunch of source examples for dialect from Guillect himself I...</summary></entry></feed>