Re: Games made with BBC BASIC for Windows

On Oct 23, 12:59 pm, Rob Kendrick <n...@xxxxxxxx> wrote:
Your you I.  Or what you wrote was a vague rambling of somebody who
doesn't know what xlib is.

I do know what xlib is. Whether or not you read what I wrote, your
reply didn't address the point I was making. It's a classic
politician's trick - don't answer the question you were asked but
answer a different one!

Sure - and how many people write installer apps?  They're a niche.

Once again you obviously didn't read (or understand) what I wrote, or
simply don't have an answer.

There are a dozen different C libraries for applications developed
under Windows.  If you don't have the right one installed, your app
won't run.  How is this different?

This really shows your ignorance about plain Win32 API programming.
For a start, C (and hence C libraries) may not be involved at all.
Secondly, even if you do use C the only library likely to be essential
is msvcrt.dll, which comes with every copy of Windows. There's no
"right one" or "wrong one", and there's no need to distribute it with
your application.

BBC BASIC for Windows executables (which is where we came in) need no
libraries other than the standard set of DLLs that come with Windows
and together make up the Win32 API. Show me a binary Linux
application which is compatible across multiple OS versions but
*doesn't* come with any libraries and I might take you more seriously.

I can understand why you are so muddled - it stems from your use of
frameworks and languages which isolate you from the native API. You
are used to executables being packaged with libraries on both OSes,
and haven't realised that whilst they are essential to achieve
compatibility across Linux versions, they aren't essential under
Windows. You said that "wanting to know what goes on under Windows's
hood is a sign of a sick mind" but if you bothered to learn about it
you would understand the difference between Windows and Linux in
respect of binary API compatibility.

Anyway, this is getting tedious. Whatever I say you will simply
counter it, ignore it or misrepresent it. I am happy for anybody
reading this thread to draw their own conclusions.

Richard.
http://www.rtrussell.co.uk/
To reply by email change 'news' to my forename.
.

Relevant Pages

  • Re: From Console to WIn32 App
    ... You can make Windows GUI programs with any compiler/IDE. ... optionally other vendor proprietary libraries (like MFC, ... You need Win32 programming tutorial. ... Windows programs using Win32 API directly. ...
    (microsoft.public.vc.language)
  • Re: Basic terminology help
    ... the Win32 API is implemented by an array ... of Windows OSes - from Windows NT 3.1 and Windows 95 ... somehow - it might be DLLs or static link libraries or web services, ... Win32 API is implemented by Microsoft Windows as well as ...
    (microsoft.public.vc.language)
  • Re: Can MS listen to customers?
    ... IE is comprised of a set of libraries that other applications use. ... a HUGE portion of even a minimal install of Windows (or even in ... For Windows, Notepad, Paint, IE, OE, msconfig, Wordpad, Hearts, NT ...
    (microsoft.public.windowsxp.general)
  • Re: Side-by-side installation on Windows 98SE and Windows 2000
    ... I was surprised to find that this is also supported on Windows 98 ... VB6 cannot create them. ... DLL Search algorithm explores at runtime. ... program (and it's libraries in the app folder) leaves behind a broken COM ...
    (microsoft.public.vb.general.discussion)
  • Re: DFPORT
    ... I work on a Windows XP platform. ... We normally use F77 Fortran and for this one problematic program we ... Since we also have the Intel Fortran compiler, we also had a lot of ... Windows Fortran comper (with appropriate libraries). ...
    (comp.lang.fortran)