Przemek,
- Original Message -
From: "Przemyslaw Czerpak" <[EMAIL PROTECTED]>
To: "Harbour Project Main Developer List."
Sent: Thursday, May 08, 2008 3:07 AM
Subject: Re: [Harbour] Re: .ppo selectively skips #line ... directives
In current PP <*id*> should work like in Clipper alloc
This is a reminder that we are in feature lockdown at this time and are ready
to release the first release candidate for Harbour Project 1.0.
I will mark the files for RC1 as soon as we have a what's new file. And that
is a big undertaking. I just don't want us to lose sight of why we are not at
Hi Guys,
When I run one of my ADS prg I got the following runtime error:
The Ordinal 468 could not be located in the dynamic link library ACE32.DLL.
Any advice please.
Cheers,
Ed
--
View this message in context:
http://www.nabble.com/ACE32-Error-tp17120163p17120163.html
Sent from the Harbou
On Wed, 07 May 2008, frank van nuffel wrote:
Hi Frank,
> indeed, and shouldn't, by all means - in the PP passes, which are ca-clipper
> passes, this is sth i took care of, similarly to what you suggest below;
> sorry i overlooked that this _PASS3 technique was used in an xharbour-only
> PP pass,
Hi Przemek,
- Original Message -
From: "Przemyslaw Czerpak" <[EMAIL PROTECTED]>
To: "Harbour Project Main Developer List."
Sent: Wednesday, May 07, 2008 4:50 PM
Subject: Re: [Harbour] Re: .ppo selectively skips #line ... directives
On Tue, 06 May 2008, frank van nuffel wrote:
[>> sn
Hi Przemek,
Well, for me it's not a problem.
Notice however that by using -q/-q0 the whole problem disappears,
as none of these messages would appear on any outputs, and
this is what I expect to happen in most "advanced" build environments
(I may be wrong though). So, IMO, -q is what you need,
On Tue, 06 May 2008, frank van nuffel wrote:
Hi Frank,
> Yes! great, this works fine - thx
Fine, I'll commit it.
> Gradually i'll explore the new pp to see whether it can replace the need for
> supplementary ca-clipper pp passes, which kind of use quite a number of
> hacks, which i don't expect
Hi Mindaugas,
I do not remember the date, but we've already had discussion on
exactly the same topic some time ago.
I think #ifdef guarded platform dependent behaviour is the only
solution, that will satisfy both DOS and Linux users.
That was about the reversed nature of std/err in non-
Szakáts Viktor wrote:
What do you think?
I cannot see that it is useful behaviour to emulate. Who does it help?
Regards
Alex
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
I'm not a DOS/Windows user and I expect that when I redirect stderr
to file then for clean builds without any warning this file will be
empty just like in all other compilers I'm using. I know that due to
missing stderr redirection in pure DOS command.com DOS compilers were
using many different ha
On Wed, 07 May 2008, Szakáts Viktor wrote:
Hi Viktor,
> Well, for me it's not a problem.
> Notice however that by using -q/-q0 the whole problem disappears,
> as none of these messages would appear on any outputs, and
> this is what I expect to happen in most "advanced" build environments
> (I ma
Two most important (from my point of view) features:
1) you can do drawing to pdf/png/ps/svg files and Windows DC/X-Win
surface using the same interface function. You just do not need to worry
if your output device is screen or pdf, etc.;
2) multiplatform.
Excellent. I assume you already have
Hi Przemek,
On 2008.05.07., at 12:46, Przemyslaw Czerpak wrote:
I'm not a DOS/Windows user and I expect that when I redirect stderr
to file then for clean builds without any warning this file will be
empty just like in all other compilers I'm using. I know that due to
missing stderr redirection
Przemyslaw Czerpak escribió:
On Wed, 07 May 2008, Miguel Angel Marchuet wrote:
It's correct. In hb_stackDispCall() (this function is used only by
internal error handler) we show only pure function names without
information about codeblocks source. If it's a problem then I can
change it to presen
Thanks Victor, now i know what to look for
Don't hesitate reverting as Przemek suggested, if that's what is better
From here on i'll manage
kind regards
frank
- Original Message -
From: "Szakáts Viktor" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, May 07, 2008 12:26 PM
Subject: [Harbou
On Wed, 07 May 2008, Miguel Angel Marchuet wrote:
> >It's correct. In hb_stackDispCall() (this function is used only by
> >internal error handler) we show only pure function names without
> >information about codeblocks source. If it's a problem then I can
> >change it to present call stack just li
It's correct. In hb_stackDispCall() (this function is used only by
internal error handler) we show only pure function names without
information about codeblocks source. If it's a problem then I can
change it to present call stack just like in hb_vmRequestCancel().
Shows EVAL instead of ERRORDIAL
On Wed, 07 May 2008, Szakáts Viktor wrote:
Hi Viktor.
Thanks for your modifications but:
>* source/compiler/hbmain.c
> * Changed output device (hb_compOutStd() -> hb_compOutErr())
>for following texts:
>"Compiling..."
>"No code generated"
>"Lines x, Func
On Wed, 07 May 2008, Miguel Angel Marchuet wrote:
> With this example we can see how call stack inform incorrect function
> at harbour...
It's correct. In hb_stackDispCall() (this function is used only by
internal error handler) we show only pure function names without
information about codeblocks
2008-05-07 11:21 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* contrib/rddads/make_b32.bat
* contrib/rddads/make_vc.bat
* contrib/rddads/ads.ch
* contrib/rddads/rddads.h
* contrib/rddads/ads1.c
* contrib/rddads/adsfunc.c
* contrib/rddads/adsmgmnt.c
+ Added ACE version a
I have very bad English.
I am happy if you (or somebody) will correct my edition
http://en.wikipedia.org/wiki/Harbour_compiler
In Wikipedia you can do pressing the "edit this page" link in top of
page
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andrze
With this example we can see how call stack inform incorrect function
at harbour...
But Why recursive error is produced too?
Best regards,
Miguel Angel Marchuet
PROCEDURE Main()
#ifdef __XHARBOUR__
REQUEST HB_GT_WIN
#endif
? Nil * "A"
RETURN
//
Hi,
28.txt file as :
line1 239845 2006-12-28 06:19:06 03 0
line2 659532 2006-12-28 06:21:08 03 0
line3 928440 2006-12-28 07:24:28 03 0
line4 938007 2006-12-28 07:24:28 03 0
hfile:=hb_Fuse("a28.txt")
?hb_feof()
// .t.
?hb_freadln()
//line1 239845 2006-12-28 06:19:06 03 0
hb_fsk
<<<
Another alternative, OSS, ANSI C, with more features
and only ZLIB and LIBPNG dependencies is Haru Free
PDF Library (libharu) by Takeshi Kanno. This one of
course needs a Harbour layer to be developed.
I have found the links. Here is what I observed:
1) HahuPDF has a lot of capabilities.
24 matches
Mail list logo
