On Sat, 12 Jan 2008, Petr Chornyj wrote:
> >> hb_stackReturnItem() is more fast than making a copy of item. In many
> >> cases hb_stackReturnItem() is OK. Maybe we can use hb_stackReturnItem()
> >> for internal code and hb_itemNew( hb_stackReturnItem() ) for public API.
> > pItem = hb_itemRet
Przemyslaw Czerpak-2 wrote:
>
> ..
>> I feel my letter is more like brainstorming before a sleep than a letter
>> of the ideas I really want to see implemented. Usage of
>> hb_stackReturnItem() is more fast than making a copy of item. In many
>> cases hb_stackReturnItem() is OK. Maybe we can
On Sat, 12 Jan 2008, Mindaugas Kavaliauskas wrote:
> what are situations and rules to use hb_itemLockReadCPtr()? Pointer to C
> string could be obtained not only by using hb_itemGetCPtr(). There is a
> number of other methods, hb_parc() is an example.
>
> HB_FUNC( MYFUNC2 )
> {
>char* szPa
Przemyslaw Czerpak wrote:
+ added new functions for string manipulation:
char * hb_itemLockReadCPtr( PHB_ITEM pItem, ULONG * pulLen );
char * hb_itemLockWriteCPtr( PHB_ITEM pItem, ULONG * pulLen );
void hb_itemUnLockCPtr( char * pszString );
It's recommended
On Fri, 11 Jan 2008, Szakáts Viktor wrote:
> Hi Przemek,
> I think there is such an unsafe usage of hb_itemGetCPtr()
> in philes.c / FREAD().
> That one sprang to my mind, but maybe there are more.
Now it's safe because hb_itemUnShareString() is used but I would like
to eliminae this functions fro
Hi Przemek,
I think there is such an unsafe usage of hb_itemGetCPtr()
in philes.c / FREAD().
That one sprang to my mind, but maybe there are more.
Brgds,
Viktor
On 2008.01.11., at 18:01, Przemyslaw Czerpak wrote:
2008-01-11 18:01 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbou
2008-01-11 18:01 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbour/include/hbapiitm.h
* harbour/source/vm/itemapi.c
+ added new functions:
BOOL hb_itemParamStore( USHORT uiParam, PHB_ITEM pItem )
BOOL hb_itemParamStoreForward( USHORT uiParam, PHB_ITEM pItem )
