In Linux:-
/home/baz/hash // current path in Linux
? curdrive()+hb_osPathSeparator()+curdir()
Returns:-
A/home/baz/hash
If curdrive() returned "" in Linux then there may be compatibility?
Where does "A" come from?
Barry Jackson wrote:
Sorry, my mistake - I did not test in Windows.
I j
Sorry, my mistake - I did not test in Windows.
I just found my old Clipper code in which:-
path_str = (DISKNAME())+":\"+(CURDIR())
Will test more in future! ;-)
Mindaugas Kavaliauskas wrote:
Hi,
Question: what this code shows in windows if current directory is set
to some //server/path/tree/
Revision: 10184
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=10184&view=rev
Author: druzus
Date: 2009-02-05 23:01:40 + (Thu, 05 Feb 2009)
Log Message:
---
2009-02-06 00:05 UTC+0100 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
* harbour/include/hbsta
AbeB wrote:
like rddinf( RDDI_CONNECTION )
and thanks again for everybody for all this work. I mean it's fascinating..
marvelous…
Hi,
rddinfo( RDDI_CONNECTION ) works very well for me. SELF CONTAINED
sample, please.
Regards,
Mindaugas
___
Harb
Hi,
Question: what this code shows in windows if current directory is set
to some //server/path/tree/file path?
? curdrive()+hb_osPathSeparator()+curdir()
C:\cawi32\sample\test>hbrun test146.prg
C\cawi32\sample\test
\\\linux\samba1
On Thu, 05 Feb 2009, Maurilio Longo wrote:
Hi Maurilio,
> I hope I've solved this one, I hade to write in os/install.cf the install rule
> this way. Note that removing the empty line inside inst_file and/or trying to
> make a for %i in ( ... ) loop causes a segfault.
> The fault is inside cmd.exe
On Thu, 05 Feb 2009, Barry Jackson wrote:
Hi Barry.
> In Linux the full path is returned with the leading "/" missing, which
> breaks compatibility with Windows code.
> Path = "/"+curdir() // Linux
> Path = curdir() // Win
Have you tested it?
> Is it possible to correct this?
In
In Linux the full path is returned with the leading "/" missing, which
breaks compatibility with Windows code.
Path = "/"+curdir() // Linux
Path = curdir() // Win
Is it possible to correct this?
___
Harbour mailing list
Harbour@harbour-pr
like rddinf( RDDI_CONNECTION )
and thanks again for everybody for all this work. I mean it's fascinating..
marvelous…
--
View this message in context:
http://n2.nabble.com/RDDADS-rddinfo%28%29-not-returning-settings.-tp2276935p2276935.html
Sent from the harbour-devel mailing list archive at Nab
Yes, it's inside one of my entries in ChangeLog as TOFIX.
I didn't want to touch that, but already searched for
toupper/tolower/islower/etc references, and there isn't
a great number of them fortunately.
I've also added Harbour API replacement for these.
Some of them currently using above function
On Thu, 05 Feb 2009, Przemyslaw Czerpak wrote:
[...]
Hi,
And one thing else much more important for me because it's
a real problem in current code which may cause unpredictable
results, f.e. some index corruption.
We should eliminate functions which uses locale settings because
they can badly chan
Hi Przemek,
> > OpenWatcom 1.8 gives hundreds of warnings for INT32.
>
> We do not have to use HB_OS_WIN_USED. It's enough to include windows.h
> before Harbour header files. We can also disable it or include it always
> in hbdefs.h this is not big problem.
> We should only add detecting of alrea
Przemyslaw,
I hope I've solved this one, I hade to write in os/install.cf the install rule
this way. Note that removing the empty line inside inst_file and/or trying to
make a for %i in ( ... ) loop causes a segfault.
The fault is inside cmd.exe, I don't understand way the previous code was
faili
On Wed, 04 Feb 2009, Szak�ts Viktor wrote:
Hi Viktor,
> What would the preferred direction we should go in order
> to avoid C type name collisions with external packages,
> and OS APIs (like Windows API)?
> Here's is an incomplete list of type names which may cause such problems:
> BOOL
> SCHAR,
Przemek
Przemyslaw Czerpak-2 wrote:
>
> Passing C structures as string is also bad idea.
> If we do not need support for direct updating C structure
> members at .prg level then it will be enough to introduce
> special type of GC pointer to hold all such structures with
> basic type veryficatio
>
> HB_USR_LIBS
Okay. [ changed to *LIBLIST last minute to avoid resemblance to *LIB. ]
> > PRG_USR -> HB_USR_PRG
>
> HB_PRGFLAGS
>
> > C_USR-> HB_USR_C
>
> HB_CFLAGS
>
> > L_USR-> HB_USR_L (or HB_USR_LINK ?)
>
> HB_LFLAGS
>
> > A_USR-> HB_USR_A (or HB_USR_LIB ?)
Il 05/02/2009 15.43, Viktor Szakáts ha scritto:
as possible WINAPI interface. If in doubt I'd personally in all
cases prefer to favour the "Harbour feel". "Harbour feel" means
that .prg programmer shouldn't be able to cause a GPF/memory
corruption using .prg level
On Thu, 05 Feb 2009, Szak�ts Viktor wrote:
Hi,
> I plan to commit this long time planned modification,
> to clear up some last non prefixed public envvars
> needed to configure Harbour:
> HB_USER_LIBS -> HB_USR_LIBLIST
IMHO HB_USER_LIBS or HB_USR_LIBS is better.
'libs' is commonly used shortcut
>
> as possible WINAPI interface. If in doubt I'd personally in all cases
>> prefer to favour the "Harbour feel". "Harbour feel" means that .prg
>> programmer shouldn't be able to cause a GPF/memory corruption using .prg
>> level WINAPI calls.
>>
>> This is ok for me, just to decide if we have to
Il 05/02/2009 15.17, Viktor Szakáts ha scritto:
Thanks for clarifying, I still agree with you.
Thank you
If you ask me, I'd rather fully ignore the explicitly passed
length parameter, as the only result of that is potential
buffer overrun and big security holes (and/or more complicated
an
>
> the name I proposed is related to MSDN syntax and to ms libs.
> To be clear in MSDN function:
> CreateCompatibleDC() is defined:
>
> Requirements
> Windows NT/2000/XP/Vista: Included in Windows NT 3.1 and later.
> Windows 95/98/Me: Included in Windows 95 and later.
> Header: Declared in Wing
Hi Pritpal, Viktor,
Il 05/02/2009 0.58, Pritpal Bedi ha scritto:
Hi
wapi_gdi32.c OR wapi_gdi.c ( removing 32, may contain gdi32 or gdi++
functions )
the name I proposed is related to MSDN syntax and to ms libs.
To be clear in MSDN function:
CreateCompatibleDC() is defined:
Requirements
W
It was about 10 years ago and written quickly for my own use - so not
really documented that well. On looking back I now recall that the
content for the pages was exported from the memo fields along with other
text and numeric data into a CSV file which was imported into a 3rd
party eCommerce p
Przemyslaw Czerpak escribió:
On Wed, 04 Feb 2009, Miguel Angel Marchuet wrote:
Hi Miguel,
(Foxpro) Code page: These values follow the DOS / Windows Code Page values.
Value Description Code page
01h DOS USA code page 437
02h DOS Multilingualcode page 850
03h Windows AN
>HB_USER_LIBS -> HB_USR_LIBLIST
>PRG_USR -> HB_USR_PRG
>C_USR-> HB_USR_C
>L_USR-> HB_USR_L (or HB_USR_LINK ?)
>A_USR-> HB_USR_A (or HB_USR_LIB ?)
>MK_USR -> HB_USR_MK (or HB_USR_MAKE/MAK ?)
Hi Viktor.
Looking at the user side, HB_USR_LINK is easy to understand
Revision: 10183
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=10183&view=rev
Author: vszakats
Date: 2009-02-05 09:21:52 + (Thu, 05 Feb 2009)
Log Message:
---
2009-02-05 10:21 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* contrib/rddado/adordd.prg
In contrib/rddado/adordd.prg there are a few places where HB_SYMOL_USED is used.
I think it was suppose to be HB_SYMBOL_UNUSED. Later when trying to link this
library
it complain about this Unresolved external.
Chen.___
Harbour mailing list
Harbour@h
Thanks Mitja, I've copied this information to the Tracker, and closed the
case as rejected.
Brgds,
Viktor
On Thu, Feb 5, 2009 at 6:58 AM, Mitja Podgornik wrote:
> Not quite...
>
> Note this change in fieldget function:
>
> ...
> if ::FieldType(nNum) == "C"
> - return PadR(::aRow[nNum], ::aField
28 matches
Mail list logo
