Mindaugas Kavaliauskas wrote:
Hi,
I expect pointer not to be collected, because it lives in variable h.
What's wrong with my code?
Best regards,
Mindaugas
PROC main()
LOCAL h
h := myfunc( h )
debug( 1 )
h := myfunc( h )
debug( 2 )
h := myfunc( h )
Hi Mindaugas,
I expect pointer not to be collected, because it lives in variable h.
No. Not always. See below ...
What's wrong with my code?
Read below ...
PROC main()
LOCAL h
h := myfunc( h )
You call h := myfunc( h ). h is empty so hb_gcAlloc()
is called in myfunc() and the result
Marek Paliwoda pisze:
And now the old item stored in h previously, does not belong
to any item and it is freed by GC.
Should be read as to any place known to GC or to any host
variable like : local,static,private,public,or hb_itemNew().
--
Marek
Jorge A. Giraldo escribió:
Ciro,
hbvm.lib
thanks Jorge
best regards
Ciro
--
http://sistemascvc.tripod.com (la casa del no2imp / the no2imp home )
http://www.oohg.org ( Object Oriented Harbour GUI, more simple, more powerfull )
___
Harbour
Hi All,
void* ptr = hb_parptrGC( hb_fctx_destructor, 1 );
Could someone explain me what is the purpose of hb_parptrGC() ?
--
Marek
--
Zmus swojego faceta, zeby to przeczytal
Kliknij http://link.interia.pl/f1ceb
Przemyslaw Czerpak pisze:
On Sat, 02 Feb 2008, Marek Paliwoda wrote:
Hi All,
void* ptr = hb_parptrGC( hb_fctx_destructor, 1 );
Could someone explain me what is the purpose of hb_parptrGC() ?
It's used for verification if given parameter holds pointer item
with pointer which points to
On Sat, 02 Feb 2008, Mindaugas Kavaliauskas wrote:
Hi,
I expect pointer not to be collected, because it lives in variable h.
What's wrong with my code?
The reference counter. Multiple putting the same pointer in
GC pointer item is not safe. If you think that it should be
safe then I can add
On Thu, 31 Jan 2008, Szakáts Viktor wrote:
Hi Przemek and all,
I've noticed this RDD doesn't get built
either using the GNU and non-GNU make system.
It's not used old DBT only code. I created new memo code
(DBFFPT) and it supports different memo types:
DBT, SMT, FPT VFP, FPT FLEX (without
Hi Przemek,
On 2008.02.02., at 14:11, Przemyslaw Czerpak wrote:
On Thu, 31 Jan 2008, Szakáts Viktor wrote:
Hi Przemek and all,
I've noticed this RDD doesn't get built
either using the GNU and non-GNU make system.
It's not used old DBT only code. I created new memo code
(DBFFPT) and it
On 2008.02.02., at 15:03, Marek Paliwoda wrote:
Marek Paliwoda pisze:
because I am an author of an original idea, and
In fact, the original author of this idea was *Ryszard*
(sorry Ryszard, I forgot this), but he only used it internally,
inside GC. What I did was exposing this idea to
2008-02-02 15:29 UTC+0100 Viktor Szakats (harbour.01 syenar.hu)
+ contrib/examples/rdddbt
- contrib/examples/dbfdbt
* Renamed after move.
--
Brgds,
Viktor
___
Harbour mailing list
Harbour@harbour-project.org
Hi,
thanks for replay.
I expect pointer not to be collected, because it lives in variable h.
What's wrong with my code?
The reference counter.
...
If you need the exact technical
answer what was wrong in your code then this is hacked version
of your code to work properly. Please never try
David Arturo Macias Corona [EMAIL PROTECTED] napisał(a):
Using
make_gnu.cmd clean
result in messages like these:
---
SYS0002: The system cannot find the file specified.
Error occurred while processing: os2\gcc*.*.
I have restored double backslash
Pritpal Bedi escribió:
Hello
Ciro Vargas Clemow wrote:
Finally the sample works ok.
Is a very good work Pritpal, excellent.
Hi Pritpal:
I don't found this files, may you sendme tbrowse and tbcolumn fix to my private
email.?
I'm very interesting in your contribution.
best regards
Ciro
Hi,
I want to consult on some fundamental thing of programming. This is a
topic of asynchronous vs. synchronous programing. Let's say I have a
code like this:
PROC server_proc(oConn)
LOCAL lOK := .F.
oConn:Send( server_version )
aData := oConn:Receive()
IF CheckPasword( aData )
Mindaugus
Mindaugas Kavaliauskas wrote:
I want to consult on some fundamental thing of programming. This is a
topic of asynchronous vs. synchronous programing. Let's say I have a
code like this:
PROC server_proc(oConn)
aData := oConn:Receive()
RETURN
It looks readable and I
16 matches
Mail list logo