Re: [MSEide-MSEgui-talk] MSElang, fixsize numeric base types

2013-11-14 Thread Michael Schnell
On 11/14/2013 09:16 AM, Michael Schnell wrote: x6: unsigned : 2; This syntax would allow for x7: unsigned : 1024; It would be a nice and consequent to provide arbitrary precision integer arithmetic :-) . -Michael

Re: [MSEide-MSEgui-talk] Unexpected firing Form.OnCloseQuery on disabling TGroupBox placed on the form

2013-11-14 Thread Ivanko B
Looks fixed :) -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any

Re: [MSEide-MSEgui-talk] Unexpected firing Form.OnCloseQuery on disabling TGroupBox placed on the form

2013-11-14 Thread Martin Schreiber
On Thursday 14 November 2013 10:28:55 Ivanko B wrote: Looks fixed :) You probably accidentally set ow1_canclosenil in your form, therefore the suggestion to remove that flag or to check the amodalresult parameter in onclosequery for mr_canclose. Both would solve the problem. Martin

Re: [MSEide-MSEgui-talk] Unexpected firing Form.OnCloseQuery on disabling TGroupBox placed on the form

2013-11-14 Thread Ivanko B
You probably accidentally set ow1_canclosenil == Most probably me misunderstood the meaning of this option - smth like alowing NULL DB-values on checking edit widgets in OnCloseQuery :) -- DreamFactory - Open

Re: [MSEide-MSEgui-talk] MSElang, fixsize numeric base types

2013-11-14 Thread Sieghard
Hallo Michael, Du schriebst am Thu, 14 Nov 2013 09:16:18 +0100: Do you intend to implement runtime range checking with any of these types ? It might not be very neccessary if these types aren't compatible among each other. Range checking has to be done only on coercion then, i.e. when

Re: [MSEide-MSEgui-talk] MSElang, compound statements

2013-11-14 Thread Sieghard
Hallo Michael, Du schriebst am Thu, 14 Nov 2013 08:56:27 +0100: the code the compiler produces may look wildly different from what the programmer expected. This is _very_ true with GNU C. When using optimization level 3, the debugger has no chance to show certain variables, as they are

Re: [MSEide-MSEgui-talk] MSElang, fixsize numeric base types

2013-11-14 Thread Sieghard
Hallo Martin, Du schriebst am Thu, 14 Nov 2013 08:12:45 +0100: The range could default to the maximum of the bit size: ... What an awkward syntax. My suggestion: don't. I don't like it. Thank you. Or with reserved words: You would have to devise a way to do the calculations, and you might

Re: [MSEide-MSEgui-talk] MSElang, compound statements

2013-11-14 Thread Sieghard
Hallo Michael, Du schriebst am Thu, 14 Nov 2013 08:50:10 +0100: The Pascal with statement was introduced with the _explicit_ intention to allow just the mentioned optimization, Since that time compiler seem to have done their homework and can do without private lessons :-) Kind of.

Re: [MSEide-MSEgui-talk] MSElang, compound statements

2013-11-14 Thread Sieghard
Hallo Marcos, Du schriebst am Wed, 13 Nov 2013 22:26:19 -0200: The compiler should provide a way to assign a directory to a 'Namespace' named by programmer, eg: Synapse. Why a directory? Why not a specific file? Or, why not allow for specifying imported units - additionally - by a

Re: [MSEide-MSEgui-talk] MSElang, fixsize numeric base types

2013-11-14 Thread Martin Schreiber
On Thursday 14 November 2013 21:39:05 Sieghard wrote: Or with reserved words: You would have to devise a way to do the calculations, and you might even get forced to provide a way to request the actual values - how could you do this if the values depend on some unspecified type? Use

Re: [MSEide-MSEgui-talk] MSElang, fixsize numeric base types

2013-11-14 Thread Martin Schreiber
On Thursday 14 November 2013 08:12:45 Martin Schreiber wrote: The range could default to the maximum of the bit size: type boolty = : 8; //bool8 cardty = 0 to: 8; //card8 intty = -to: 8;//int8 charty = #0 to: 8; //char8 floatty = -. to .: 64; //flo64