It strikes me that whilst it may not be the best programming form, the
same thing could be done readily with a global variable?
M.
Tom Walsh wrote:
Mark Wood wrote:
I have found that there are some functional differences that
Metaware has over
fpc, one example is the yield() function which
Tom Walsh wrote:
Mark Wood wrote:
I have found that there are some functional differences that
Metaware has over
fpc, one example is the yield() function which returns the
intermediate result
of a function call.
?
'?' indeed! I am fascinated! What does yield do exactly... presumably
memsom wrote:
'?' indeed! I am fascinated! What does yield do exactly... presumably it
returns a result from the function without closing down that instance of
the function? Amazing concept.
I suspect - given the word "DOS" in some of the code, it allows a DOS
event loop to continue in a s
Mark Wood wrote:
I have found that there are some functional differences that Metaware has over
fpc, one example is the yield() function which returns the intermediate result
of a function call.
?
'?' indeed! I am fascinated! What does yield do exactly... presumably
it returns a resul
> Nope. It's that what Mark thinks, and more like (Python's) generator
> thingie (link posted by Luca):
Rght.. like:
insert into blah (test) values(1);
insert into blah (test) values(2);
insert into blah (test) values(3);
insert into blah (test) values(4);
create procedure test()
returns(r
On Tuesday 19 June 2007 11:48, memsom wrote:
> > '?' indeed! I am fascinated! What does yield do exactly...
> > presumably it returns a result from the function without closing
> > down that instance of the function? Amazing concept.
>
> I suspect - given the word "DOS" in some of the code, it allo
> '?' indeed! I am fascinated! What does yield do exactly... presumably it
> returns a result from the function without closing down that instance of
> the function? Amazing concept.
I suspect - given the word "DOS" in some of the code, it allows a DOS
event loop to continue in a single threaded c
Flávio Etrusco wrote:
There are many Portuguese speakers in the list that certainly will be
glad to help too ;-)
Best regards,
Flávio (from Brazil)
Yup. I have started a thread in the Lazarus mailing list where only
PT-BRs participated. =)
--
Joao Morais
En/na Mark Wood ha escrit:
I have found that there are some functional differences that Metaware has over
fpc, one example is the yield() function which returns the intermediate result
of a function call.
?
'?' indeed! I am fascinated! What does yield do exactly... presumably it
retu
On 19 jun 2007, at 10:50, Felipe Monteiro de Carvalho wrote:
I just suposed that on the backtrace gdb would show exactly where the
exception occured. There were more functions called at the point where
the exception really happens ... I don't know why he skiped some.
Debuging with the IDE step-
On 6/19/07, Jonas Maebe <[EMAIL PROTECTED]> wrote:
Without compilable example code, that is impossible to say.
Sorry for the noise, I found the problem =)
Inside the DrawTo function code there is a cast to an interface which
isn't implemented.
I just suposed that on the backtrace gdb would sh
I have found that there are some functional differences that Metaware has over
fpc, one example is the yield() function which returns the intermediate result
of a function call.
?
'?' indeed! I am fascinated! What does yield do exactly... presumably it
returns a result from the functi
On 18 jun 2007, at 22:06, Felipe Monteiro de Carvalho wrote:
Breakpoint 1, 0xe0a6 in fpc_raiseexception ()
(gdb) bt
#0 0xe0a6 in fpc_raiseexception ()
#1 0x00056682 in SYSUTILS_RUNERRORTOEXCEPT$LONGINT$POINTER$POINTER ()
#2 0x00010fd7 in SYSTEM_HANDLEERRORADDRFRAME$LONGINT$POINTER
$
On 18 jun 2007, at 19:48, Vincent Snijders wrote:
Is it our fault that we call CheckSynchronize nested (i.e.
indirectly from a synchronized method) or is a CheckSynchronize not
smart enough not to call the synchronized method (i.e MyMessage)
twice, even if Synchronize is called only once f
14 matches
Mail list logo
