Clipper debugger....

Laszlo VIGH HERMAN

unread,

Feb 25, 2010, 10:22:55 PM2/25/10

to

Hi,

I used to have a library that I compiled with my clipper code to
debug.

I think it was CLD.LIB, yet can't find it. Any one know if it is the
library I need and where could I find one from, please.

Cheers,

Laszlo.

dlzc

unread,

Feb 26, 2010, 9:16:55 AM2/26/10

to

Dear Laszlo VIGH HERMAN:

On Feb 25, 8:22 pm, Laszlo VIGH HERMAN <las...@comdotcom.com.au>
wrote:

What version of Clipper are you using?

If you switch to xHarbour now, it comes with a debugger...
www.xharbour.org (free)
www.xharbour.com (commercial)
... and depending on which 3rd party libs you've used, you could be up
and running in a very short time, with Clipper 5.3 code.

David A. Smith

tom knauf

unread,

Feb 26, 2010, 9:21:45 AM2/26/10

to

Hi,

I think, you are right, its cld.lib
Put an ALTD() in the code to start debugging there

HTH
Tom

"Laszlo VIGH HERMAN" <las...@comdotcom.com.au> schrieb im Newsbeitrag
news:600fbb06-16b5-4e99...@b5g2000prd.googlegroups.com...

Texextra

unread,

Feb 26, 2010, 10:36:36 AM2/26/10

to

On Feb 25, 9:22 pm, Laszlo VIGH HERMAN <las...@comdotcom.com.au>
wrote:

It should be in your LIB directory. Link it in as a file, last. As Tom
said, you'll probably want to include an altd() in your code. I also
copy CLD.LIB into my OBJ directory.

Something like this: BLINKER @MYLINK.LNK FI CLD.LIB or BLINKER FI
MYPROG FI CLD.LIB

dlzc

unread,

Feb 26, 2010, 11:59:17 AM2/26/10

to

Dear Texextra:

On Feb 26, 8:36 am, Texextra <texex...@gmail.com> wrote:
> On Feb 25, 9:22 pm, Laszlo VIGH HERMAN <las...@comdotcom.com.au>
> wrote:

...

> > I think it was CLD.LIB, yet can't find it.
>

> It should be in your LIB directory.

I think (using my psychic powers) he is saying the file has been
deleted, sometime prior to him asking (indirectly) if someone can
"loan" him a copy. He still needs to tell us what version of Clipper
he is using...

David A. Smith

Laszlo VIGH HERMAN

unread,

Feb 26, 2010, 9:30:34 PM2/26/10

to

Hi All,

Thank you for all the feedback and info.

I would be interested in xHarbour, only it maybe too long before
checking through all the codes to make it work in the new environment.
I am saying this, with out knowing much about the work that would
involve...

YES, I can not find the CLD.lib!!! I know it was around and can not
find it now. Programs have been working fine for many-many years with
out being touched, yet now need to take them further a little, so the
debugging would be a must.

Using Clipper 87(Clipper LIB is 21/12/87, if it is any help...???

Would be happy to buy the whole software again, if it is for sale in
an electronic way.

Cheers,

Laszlo.

Laszlo VIGH HERMAN

unread,

Feb 26, 2010, 10:47:52 PM2/26/10

to

By the way, I just found some old disks, Clipper 5.2...
Is the CLD.lib from there could/would work with Clipper 87?

pe...@nospam.demon.co.uk

unread,

Feb 27, 2010, 2:37:36 AM2/27/10

to

In article <4eee84d7-e684-418e...@w27g2000pre.googlegroups.com>

las...@comdotcom.com.au "Laszlo VIGH HERMAN" writes:

> Hi All,
>
> Thank you for all the feedback and info.
>
> I would be interested in xHarbour, only it maybe too long before
> checking through all the codes to make it work in the new environment.
> I am saying this, with out knowing much about the work that would
> involve...
>
> YES, I can not find the CLD.lib!!! I know it was around and can not
> find it now. Programs have been working fine for many-many years with
> out being touched, yet now need to take them further a little, so the
> debugging would be a must.
>
> Using Clipper 87(Clipper LIB is 21/12/87, if it is any help...???

Hi Laszlo,

Are you sure you are looking for the right filename? There is no
CLD.LIB in my S87 either, but there is a DEBUG.OBJ:

DEBUG OBJ 57,986 21/12/87 2:00

> Would be happy to buy the whole software again, if it is for sale in
> an electronic way.

I must admit though that I never got along with the S87 debugger; much
simpler to create/open a log file on program startup and to sprinkle
new code with descriptive fwrite() statements which can be reviewed
later. [Or even better if you're developing on e.g. WinXP, open a
second command window and 'tail -f logfile' there. I've not tried this
because I used only DOS when working with S87, but it should work.]

Of course, this bloats your code somewhat, so I wrote a preprocessor
[C-style] and included the debug code in #if/#endif blocks so that
this code would not be included in the production build. If I can
still find it, you're welcome to a copy of FPP -- pretty basic but
does allow you to include code like

#if DEBUG
loghandle = fcreate ("app.log")
#endif
...
#if DEBUG
fwrite (loghandle, "Entering func: param = " + filename + CRLF)
#endif

and so on. Let me know if you're interested...

Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."

Gerhard Bunzel

unread,

Feb 27, 2010, 7:04:23 AM2/27/10

to

Hi Lazlo,

you have to use DEBUG.OBJ for debugging in Clipper S87.

HTH

Gerhard

"Laszlo VIGH HERMAN" <las...@comdotcom.com.au> schrieb im Newsbeitrag

news:4eee84d7-e684-418e...@w27g2000pre.googlegroups.com...

Patrick Mast

unread,

Feb 27, 2010, 2:29:03 PM2/27/10

to

Hello,

> I would be interested in xHarbour, only it maybe too long before
> checking through all the codes to make it work in the new environment.
> I am saying this, with out knowing much about the work that would
> involve...

In most cases its just a recompile off all your PRG code.
Do you use any 3rd party libraries with your current Clipper app?

Patrick

dlzc

unread,

Feb 27, 2010, 4:41:10 PM2/27/10

to

Dear Patrick Mast:

He's running S'87 code. Would be major differences. Not too likely
he has 3rd party libs here... there were some.

David A. Smith

Laszlo VIGH HERMAN

unread,

Mar 10, 2010, 7:22:54 PM3/10/10

to

Hello Everyone,

Thank you all for the help and suggestions!

I was just trying to follow some leads and old memories, where I knew
that if I compile in an extra LIB, or as I am corrected now, OBJ, than
I can debug in an easier way...

I have looked, and not even the DEBUG.OBJ is there, so I'll be keep
looking, as well as, I will try all the Pete's suggestion.

Onec again, thank you all for being so helpful.

Cheers,

Laszlo.

cal

unread,

Mar 12, 2010, 11:03:33 AM3/12/10

to

Laszlo,

Sorry for taking so long to respond to your message. I just happened
on the thread today and spotted your last post.

I have Clipper Summer 87 on my server HDD and in the OBJ folder I have
debug.obj. Will this help you?

Anyone: is there any reason I should not send this to Laszlo? Would
I be doing anything less that acceptable?

Cal

Laszlo VIGH HERMAN

unread,

Mar 13, 2010, 12:40:10 AM3/13/10

to

Hi Cal,

As you have asked the group, if it is not illegal, would be a great
help.

If it is an issue, I am still on the market to buy a full pack if
there is one for sale by someone.

Cheers,

Laszlo.

Geoff Schaller

unread,

Mar 13, 2010, 1:22:13 AM3/13/10

to

Laszlo,

Is there a reason you need to cling to such an old version? 5.03 is for
sale from GrafXSoft in Florida. It would not be too hard to upgrade your
app and then rebuild indexes etc.

Geoff

"Laszlo VIGH HERMAN" <las...@comdotcom.com.au> wrote in message
news:d6af20ca-cb81-44a3...@a16g2000pre.googlegroups.com:

Texextra

unread,

Mar 15, 2010, 12:08:26 PM3/15/10

to

On Mar 13, 1:22 am, "Geoff Schaller"

<geo...@softxwareobjectives.com.au> wrote:
> Laszlo,
>
> Is there a reason you need to cling to such an old version? 5.03 is for
> sale from GrafXSoft in Florida. It would not be too hard to upgrade your
> app and then rebuild indexes etc.
>
> Geoff
>

> > Laszlo.- Hide quoted text -
>
> - Show quoted text -

I assume you mean 5.3. I wouldn't want 5.3. Maybe xHarbour would be an
option.