Vic,
I did not say that line numbers are a minor issue, rather I said that
the specific issue reported is minor, because it involves 2 rare
conditions. Either-way this should be easy to fix.
Ron
On Jul 12, 2008, at 12:28 PM, Vicente Guerra wrote:
> On Thu, 10 Jul 2008, Ron Pinkas wrote:
>>
On Thu, 10 Jul 2008, Ron Pinkas wrote:
> There's also
> a report about minor issue with line numbers which I need to review.
> [...]
> None of these I consider a Release stoppers,
I'm sorry, but I don't agree. Wrong line numbers converts debugging
into a nightmare. It can be functional for be
creveu:
>
>> De: Ron Pinkas <[EMAIL PROTECTED]>
>> Assunto: Re: [xHarbour-developers] ChangeLog,v 1.6169 2008/07/10
>> Para: [EMAIL PROTECTED]
>> Cc: "Xharbour-Developers List" > [EMAIL PROTECTED]>
>> Data: Quinta-feira, 10 de Julho de 20
/7/08, Ron Pinkas <[EMAIL PROTECTED]> escreveu:
> De: Ron Pinkas <[EMAIL PROTECTED]>
> Assunto: Re: [xHarbour-developers] ChangeLog,v 1.6169 2008/07/10
> Para: [EMAIL PROTECTED]
> Cc: "Xharbour-Developers List"
> Data: Quinta-feira, 10 de Julho de 2008, 16:12
RP>> All should compile Ok, with MSVC, what error did you get?
PT> contrib\gtwvg\wvtcore.c(178) : error C2664: 'OleLoadPicture' : cannot
PT> convert parameter 4 from 'const IID *' to 'const IID &'
PT> Reason: cannot convert from 'const IID *' to 'const IID'
PT> No constructor
RP> All should compile Ok, with MSVC, what error did you get?
contrib\gtwvg\wvtcore.c(178) : error C2664: 'OleLoadPicture' : cannot
convert parameter 4 from 'const IID *' to 'const IID &'
Reason: cannot convert from 'const IID *' to 'const IID'
No constructor could take the sour
Paul,
All should compile Ok, with MSVC, what error did you get?
Ron
On Jul 10, 2008, at 2:07 PM, Paul Tucker wrote:
> Ron,
>
>> Mostly I wait on Paul for some minor GT issues [Paul?].
>
> I updated my system from CVS the other day and the compilation
> failed - I
> have yet to look into why.
Ron,
>Mostly I wait on Paul for some minor GT issues [Paul?].
I updated my system from CVS the other day and the compilation failed - I
have yet to look into why. I'll figure that out this week sometime.
Meanwhile, I've lost all messages from about Feb 17 2008 to July 7th due to
an Outlook Ex
Patrick,
Mostly I wait on Paul for some minor GT issues [Paul?]. There's also
a report about minor issue with line numbers which I need to review.
There's 1 report about FINALLY which I need to review. Finally I
believe there's a GPF trap in Macro Compiler, related to doubly freed
string v
Ron,
How close is current CVS code from a "OK for release" state?
Patrick
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a he
Eduardo,
Many thanks. :-)
BTW, there's no need to disallow TBrowse():New(), it does not break
any compatibility to have such support. OTOH removing this support
breaks compatibility with existing xHarbour code, without giving us
any advantage. All xHarbour classes should support the New() m
* source\rtl\tbrowse.prg
* This new TBrowse code was strongly modified to fix pending bugs,
to speed-up navigation under files with more than 64 columns and
general optimizations.
* From today, don't use TBrowse():New() syntax. This is not Clipper
compliant. Use TBrowse
12 matches
Mail list logo
