On Tuesday 12 November 2013 08:55:38 Ivanko B wrote:
Is it called because the form looses input focus?
==
There's no user interaction (where the form may loss input focus)
between OnEventLoopStarted and disabling widget in code. And why does
it only happens on disabling groupboxes
On 11/11/2013 11:03 PM, Sieghard wrote:
t _even_ C has block delimiters ({ and }), because they're
_needed_ by any notation that does _not_ restrict formatting the code.
In fact I _always_ use begin ... end ( or in C } ... { ) with if
and loop instructions (as I do not like the ambiguity
On 11/11/2013 11:00 AM, Ivanko B wrote:
That signedness isn't more than just a old (and not obvious) assumption.
Thus -1 is greater than 1 as the representation of -1 is all bits set ?
-Michael
--
November Webinars for
On Tuesday 12 November 2013 09:19:37 Michael Schnell wrote:
I suppose here the new compiler would accept just else begin. Does not
look bad, but not a real improvement, IMHO.
I do more like to make the end's mandatory. Like
'if' BOOLEANEXPRESSION 'then'
[STATEMENT {';' STATEMENT}]
['else'
On Tuesday 12 November 2013 09:54:11 Michael Schnell wrote:
With my background of C fro me the ; is necessary to close a
statement. This I never do a line that does not end with either of ;
or begin
In Pascal (and in MSElang) ';' does not terminate but separate a statement.
Empty statements
On 11/12/2013 10:13 AM, Martin Schreiber wrote:
In Pascal (and in MSElang) ';' does not terminate but separate a statement.
Exactly. (Different from C.)
Empty statements are possible -
OK. Thus my (c-influenced) style is acceptable.
-Michael
it this project is created immediately (w/o leaving IDE) after closing
another project.
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
On Tuesday 12 November 2013 12:38:15 Ivanko B wrote:
it this project is created immediately (w/o leaving IDE) after closing
another project.
Can not reproduce.
Martin
--
November Webinars for C, C++, Fortran
Works OK in a simple project.
Should me prepare the PODPISKA full testcase instead ?
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
win-32 ?
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from
Hi,
Here examples of the planned compound statements. Additional ';' after
statements are possible, they are treated as empty statements.
begin
a:= 1;
b:= 2
end;
with rec1:r do
r.field1:= 123
end;
with rec2:r,r.field1:s do
r.field1.field1:= 123; //or
s.field1:= 123;
end;
if a = 1 then
With arbitrary ;, how about a kind of the Python syntax - that's
w/o garbage then, do end statements ?
Currently it's emulated like :
function http_file_size(const http: thttpsend; const url: msestring;
var filesize: integer; var hdrsize: cardinal): treqresult;
var
i:integer;
Additional ';' after statements are possible, they are treated as
empty statements.
==
Like in BASH TCL ? A good idea :)
--
November Webinars for C, C++, Fortran Developers
Accelerate application
Did you model the showmodal call?
==
Is it it ?
-
procedure tmainfo.goexec(const sender: TObject);
begin
try
application.createform(tworkfo, workfo);
workfo.show(true); // HERE
finally
freeandnil(workfo);
end;
end;
On Tuesday 12 November 2013 13:43:51 Ivanko B wrote:
Additional ';' after statements are possible, they are treated as
empty statements.
==
Like in BASH TCL ? A good idea :)
Like in Pascal. ;-)
Martin
On Tuesday 12 November 2013 13:50:20 Michael Schnell wrote:
On 11/12/2013 01:25 PM, Martin Schreiber wrote:
Hi,
Here examples of the planned compound statements.
This looks as if the compiler ignore line breaks.
Correct ?
Yes, line breaks are WHITESPACE as in Pascal.
Martin
On Tuesday 12 November 2013 13:58:59 Ivanko B wrote:
Did you model the showmodal call?
==
Is it it ?
-
procedure tmainfo.goexec(const sender: TObject);
begin
try
application.createform(tworkfo, workfo);
workfo.show(true); // HERE
finally
It seems that me couldn't catch this problem because stepped debugging
breaks the form modality sequence. With changing BP placement to
traverse this sequece w/o stepping, it's found that the focus loss
happened when disabling the below widget, before calling
window.setfocusedwidget(nil):
On Tue, Nov 12, 2013 at 9:25 AM, Martin Schreiber mse00...@gmail.com wrote:
Hi,
Here examples of the planned compound statements. Additional ';' after
statements are possible, they are treated as empty statements.
[...]
with rec1:r do
r.field1:= 123
end;
with rec2:r,r.field1:s do
'namespaces'
=
In C, it's mainly designed to combine a single unit from several
simplier mixed ones to simulate the Pascal unit-ing.
Pascal also offers the unit.ident access syntax which is a namespace in sense.
On Tue, Nov 12, 2013 at 11:10 AM, Ivanko B ivankob4m...@gmail.com wrote:
'namespaces'
=
In C, it's mainly designed to combine a single unit from several
simplier mixed ones to simulate the Pascal unit-ing.
Pascal also offers the unit.ident access syntax which is a namespace
On Tuesday 12 November 2013 14:37:41 Marcos Douglas wrote:
PS: What do you think about 'namespaces' as we talked on official
pascal list? Could exist in MSElang?
Unit alias will be supported.
Martin
--
November
On Tuesday 12 November 2013 14:37:41 Marcos Douglas wrote:
On Tue, Nov 12, 2013 at 9:25 AM, Martin Schreiber mse00...@gmail.com
That is a good idea after all.
Pascal has the 'absolute' keyword so maybe could be:
with rec1 absolute r do
r.field1:= 123
end;
Maybe use 'alias' keyword
On Tue, Nov 12, 2013 at 12:45 PM, Martin Schreiber mse00...@gmail.com wrote:
On Tuesday 12 November 2013 14:37:41 Marcos Douglas wrote:
On Tue, Nov 12, 2013 at 9:25 AM, Martin Schreiber mse00...@gmail.com
That is a good idea after all.
Pascal has the 'absolute' keyword so maybe could be:
On Tuesday 12 November 2013 18:19:56 Marcos Douglas wrote:
with r:= rec1 do
r.field1:= 123
end;
with r:= rec2, s:= r.field1 do
r.field1.field1:= 123; //or
s.field1:= 123;
end;
NO! Only if r was defined. But in that case I don't see any advantages.
If I can vote using
On Tuesday 12 November 2013 13:25:05 Martin Schreiber wrote:
if c = 0 then //I am not happy with that additional check
for a in 0..c do
b:= b + ar[a]
end
end;
or
for a in 0 to c do
b:= b + ar[a]
end;
for a in c downto 0 do
b:= b + ar[a]
end;
- '..' in ranges would be replaced
On Tue, Nov 12, 2013 at 3:13 PM, Ivanko B ivankob4m...@gmail.com wrote:
I vote in with r: rec1 do
Me too :) Or
-
with rec1 as r do
I thought about that too. But it's better using the operator as only
for casting.
or Python-like
with rec1 as r:
On Tuesday 12 November 2013 19:48:03 Marcos Douglas wrote:
On Tue, Nov 12, 2013 at 12:39 PM, Martin Schreiber mse00...@gmail.com
wrote:
On Tuesday 12 November 2013 14:37:41 Marcos Douglas wrote:
PS: What do you think about 'namespaces' as we talked on official
pascal list? Could exist in
On Tuesday 12 November 2013 18:27:49 Patrick Goupell wrote:
Hello Martin,
A tsqlstatement has a params.parambyname ('fieldname').asdate method
but a tmsesqlquery does not have a params.parambyname
('fieldname').asdate method.
It does have a params.parambyname ('fieldname').asdatetime
On Tuesday 12 November 2013 20:27:24 Patrick Goupell wrote:
On 11/12/2013 02:16 PM, Martin Schreiber wrote:
procedure tmainfo.creexe(const sender: TObject);
var
dat1: tdatetime;
begin
dat1:= tsqlresult1.params.parambyname('abc').asdate;
dat1:=
Hallo Martin,
Du schriebst am Tue, 12 Nov 2013 08:33:29 +0100:
The C-like syntax
FIELDNAME ':' FIELDTYPE [':' BITSIZE] ';'
is accepted?
It's much more broadly used than just with C. In fact, C seems to have it
adopted only recently. You might use alternate delimiters, though.
Is a
Hallo Martin,
Du schriebst am Tue, 12 Nov 2013 10:19:38 +0100:
Is a record with BITSIZE automatically bitpacked?
I gather this does make sense.
I am not sure. I don't like implicit things much.
That's right - but bitsize specifications aren't really useful without
packing. But you
Hallo Michael,
Du schriebst am Tue, 12 Nov 2013 09:30:11 +0100:
On 11/11/2013 11:00 AM, Ivanko B wrote:
That signedness isn't more than just a old (and not obvious) assumption.
Thus -1 is greater than 1 as the representation of -1 is all bits set ?
You may define an ordering relation where
Hallo Martin,
Du schriebst am Tue, 12 Nov 2013 08:09:42 +0100:
MSEide editor is not limited to fixed pitch fonts so column blocks may be
Column blocks simply don't make sense with proportional fonts.
Source code can in principle be written with proportional fonts, but even
that doesn't make
Hallo Martin,
Du schriebst am Tue, 12 Nov 2013 13:25:05 +0100:
Here examples of the planned compound statements. Additional ';' after
statements are possible, they are treated as empty statements.
Like with Pascal.
with rec1:r do
r.field1:= 123
end;
Does that suggest the Oberon with,
Hallo Marcos,
Du schriebst am Tue, 12 Nov 2013 12:20:45 -0200:
Yes. But the problem is if you have two units, both using the same
name, and you want to use them at the same project.
As I said before in official list, I have -- for many years -- units
that have the prefix 'M' so, I have
On Tue, Nov 12, 2013 at 8:28 PM, Sieghard s_c_...@arcor.de wrote:
Hallo Marcos,
Du schriebst am Tue, 12 Nov 2013 12:20:45 -0200:
Yes. But the problem is if you have two units, both using the same
name, and you want to use them at the same project.
As I said before in official list, I have
On Tuesday 12 November 2013 20:24:07 Sieghard wrote:
[...]
As said above, that depends on the implementation or rather the likings of
the implementor. If more people than just the implementor are to use it, it
just needs to be documented. After all, endiandness issues are notoriously
tricky,
On Tuesday 12 November 2013 21:28:54 Martin Schreiber wrote:
The question is TParam has AsDate, why has TField AsDateTime only?
Both are FPC classes, I assume it is because of Delphi compatibility. I'll
add asdate and astime to the MSEgui version of TField.
Done, git master
39 matches
Mail list logo
