> If you can submit the smallest possible code fragments which display the
> bad behavior, it would help the debugging process.
Ok. Below are two samples.
1) The code:
// --
CLASS HDBRecSet
DATA aRecs// line1
// line2
Alexander S.Kresin wrote:
Paul,
Hi Alexander and All,
I ported Click to Harbour for use on Linux. The code is untested on
Windows but may compile and run. Added "Calls to" information in
function headers and made stand alone executable. Need to update
code in few days but current source
Paul,
Hi Alexander and All,
I ported Click to Harbour for use on Linux. The code is untested on
Windows but may compile and run. Added "Calls to" information in
function headers and made stand alone executable. Need to update code
in few days but current source and bin is posted on Googl
On Fri, May 22, 2009 at 12:26 PM, Alexander S.Kresin
wrote:
>> Yesterday I was thinking of committing a recently written
>> reindentor :)
>
> I had a feeling that I must hurry :)
> Mine for now, if it is pointed in options, indents source, changes case of
> commands, functions and booleans, ins
Yesterday I was thinking of committing a recently written
reindentor :)
I had a feeling that I must hurry :)
Not a full blown formatter (like my tool 'DST'
was trying to be, written 17 years ago), but it can change
indentation (including continued lines), it assumes a properly
and consistent
