-Messaggio Originale-
Da: "Viktor Szakáts"
A: "Harbour Project Main Developer List."
Data invio: mercoledì 25 febbraio 2009 23.17
Oggetto: Re: [Harbour] Proposing hbwhat for removal
Personally I used hbwhat only for SetErrorMode() that I just replaced with a
My opinion is the same as last year. hbdoc and
also the docs we have in their current format is a
dead end. It's not the goal of this project to develop
a documentation tool, so ideally we should choose
an existing tool, convert what we have, and delete
hbdoc.
This needs a one time effort and cont
What do you think about hbdoc?
Other old module in black list?
2009/2/25 Viktor Szakáts :
> Thanks for the feedback to all.
> It seem we agree on disabling it now, and keeping it
> for reference, and also to encourage 3rd parties to give
> feedback on whether they use it or not. AFAIK no "major"
>
Thanks for the feedback to all.
It seem we agree on disabling it now, and keeping it
for reference, and also to encourage 3rd parties to give
feedback on whether they use it or not. AFAIK no "major"
3rd party needs it, but let's hear them words.
Notice however that if we keep it in repository, it
Hi Przemek,
Il 25/02/2009 22.33, Przemyslaw Czerpak ha scritto:
if someone is interested then I can add to HVM support for
sending messages to pointer items. At least on C level.
if you find spare time to add it will be useful.
TIA
Best regards,
Francesco
__
On Wed, 25 Feb 2009, Pritpal Bedi wrote:
Hi Pritpal,
> Przemek, Mindaugus can surely come up with same solution but
> with better internal overhaul of the concept so that the potential
> "dangers" discussed can be reduced to bare minimum.
I'm not against the idea of creating some .prg level cod
Hello Francesco
Francesco Saverio Giudice wrote:
>
> BTW I'm locked on structure handling. Without a solution on it or
> without a standardization on passing values it will be a stopping point
> in hbwin developing.
> I have tried Przemek's proposal, but it's very difficult to handling
> par
Viktor
Here I endorse Francesco's observation.
What32 has always been an inspiration to me, and
probably for some others also. Whatever I could do
till date on Windows platform is due to What32 only.
It is always a source of references whenever I need
one.
So I strongly resist that it should
Hi Viktor,
Il 25/02/2009 17.04, Viktor Szakáts ha scritto:
Hi all,
hbwhat was a notorious build-breaker since it has been
added, and despite the efforts trying to fix it, it still is.
Since it has no real users either, we miss feedback
and besides making it build, we cannot be sure it even
On Wed, 25 Feb 2009, Szak�ts Viktor wrote:
Hi,
> hbwhat was a notorious build-breaker since it has been
> added, and despite the efforts trying to fix it, it still is.
[...]
> So, I'd like to propose to remove it from the repository.
> Any objections or opinions on that?
I'd suggest to disable t
Ok for me
I suggest think now which other library are in same situation
so not wasting time for in future abandon
2009/2/25 Viktor Szakáts :
> On Wed, Feb 25, 2009 at 6:29 PM, Massimo Belgrano
> wrote:
>>
>> What about maintain hbwhat only for win32 platform?
>> will takes few efforts to mainta
On Wed, Feb 25, 2009 at 6:29 PM, Massimo Belgrano wrote:
> What about maintain hbwhat only for win32 platform?
> will takes few efforts to maintain it?
It took a huge effort from my side, with _no_ benefit,
and I mean not just no benefit for me, because I don't
need it at all, but no benefit fo
What about maintain hbwhat only for win32 platform?
will takes few efforts to maintain it?
2009/2/25 Viktor Szakáts :
> Hi all,
> hbwhat was a notorious build-breaker since it has been
> added, and despite the efforts trying to fix it, it still is.
> Since it has no real users either, we miss fe
Hi all,
hbwhat was a notorious build-breaker since it has been
added, and despite the efforts trying to fix it, it still is.
Since it has no real users either, we miss feedback
and besides making it build, we cannot be sure it even
works. Since there were several bugs found in it, and
no one fixed
14 matches
Mail list logo
