Do you know how to program using the win32 API? Not same vague idea, not
just read wikipedia, not just used an automatic interface builder, but
have written a real-world application at the source code level? Do you
understand the windows message loop, understand how to send and handle
windows messages?
If no, then there is no point continuing this conversation, and this
applies to both Davids. If no, your attempt to look through the curses
source code files is silly, because you don't know what to look for.
If yes, then you should be able to provide some specific lines of code
in those source files you mention.
To answer your question, yes, I did look in the win32con directory
inside the ncurses source code, and I'm sorry, I don't see any evidence
to support the contention that 'curses programs use the Win32 API "under
the hood"', which has now been asserted for about a week with no lines
of code cited. Similarly, the other strong assertion, that "curses uses
stdin, stdout, and stderr", has been sitting around for a week with no
curses functions cited.
You say there is a "a large amount of evidence" without providing any
specifics. That's ridiculous. You are making the assertion. If there is
so much evidence, it's your responsibility to cite specific lines of
code from those files that support your argument. If I'm wrong, I'll
readily admit it. I'd be overjoyed to learn something. Why so coy and
stingy with evidence?
To make sure we are talking about the same files, which have never been
exactly specified by either David, I see three files (below). I assume
you are referring to win_driver.c file. If not, then please give me a
full path for the file(s) you are referring to.
$ wc *.c
54 337 2717 gettimeofday.c
50 315 2707 wcwidth.c
2264 5999 51510 win_driver.c
I cannot go through these files line by line to prove that each line
does not "use the win32 api". In contrast, all you need to do is cite a
few lines that "use the win32 api", and I would be happy to reconsider.
It's not really my job to explain all this, and this is way off topic
from anything to do with MSYS2. However, assuming that you are willing
to learn anything, I think where you are confused is that the directory
name "win32con", with that "win32" in it, refers to "win32 console", the
technical name for the "command prompt". The win_driver.c file also has
the string "win32" in it several times, but again it refers to the
"win32 console", not the "win32 api".
For the record, win32 api and curses are different technologies, there
is no overlap in their function calls, neither is a subset of the other.
Now of course the "win32 console" is programmed using the win32 api. But
that is a totally different issue. You assert that the source code files
show "ncurses uses the Win32 API". Please cite a line or two.
Again, I apologize to the group. I never brought up these claims that
curses somehow "uses the win32 api" or "uses stdin, stdout, and stderr".
I am happy to respond to specific arguments, but otherwise this is a
waste of time.
Daniel
On 2/17/2016 10:41 AM, David Grayson wrote:
> On Tue, Feb 16, 2016 at 11:05 PM, Daniel Goldman <[email protected]> wrote:
>> On 2/10/2016 11:15 PM, David Macek wrote:
>> > Even curses programs use the Win32 API
>> > "under the hood". See pdcurses source directory
>> > `win32` and ncurses source directory `win32con`.
>>
>> I forgot to respond to this one from your previous post. I'm sorry, but
>> I believe this is another error / false statement on your part. This is
>> a tangential issue. But you brought it up, you raised the issue.
>>
>> I'm sorry, but to my knowledge curses programs do not "use the Win32 API
>> under the hood". The metaphor (under the hood) suggests you have deep
>> knowledge on the subject. I'm sorry, I see no evidence of that.
>
> I see a large amount of evidence that ncurses uses the Win32 API when
> I look in the win32con directory inside the ncurses source code, as
> suggested by David Macek. Did you try looking there?
>
> --David
>
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
