Re: interface



begi <begi2010@xxxxxxxxx> schrieb:
Thanks for your immediately reply.
what do you think of C++ as language for speak with electronics device?

That's also a good choice.

I would like create software with visual c++ for read and write electronics
board (medical instruments).

I strongly recommend using a free compiler (e.g. GCC) and developing
under a unix-like environment. Otherwise you won't be able to write
portable code. Even when you are developing under Windows, you might
want to take a look at MSYS/DevC++ or Cygwin. It's also generally a
good idea to use a portable GUI-toolkit such as GTK, Qt or wxWidgets.
Don't mess around with the Windows API.

For communicating with an external device it's also usually a good
idea to split your program into a command line tool which does most
of the work, and a GUI that uses this tool.

Otherwise you'll write yet another windows-only GUI+logic-mangled
hard-to-test absolute-positioned-GUI application that will satisfy
its initial purpose but won't be usable for any other application
or any other operating system. Don't give up that freedom just
because you only know Visual C++. Learn more. The restrictions
you are setting up now will hurt you in the future.


Greets,

Volker

--
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR
.



Relevant Pages

  • Re: interface
    ... what do you think of C++ as language for speak with electronics device? ... Writing portable code has nothing to do with the operating system or ... independent of which operating system you are using. ... If it is meant to run on Windows only, ...
    (comp.programming)
  • Re: interface
    ... what do you think of C++ as language for speak with electronics device? ... I strongly recommend using a free compiler and developing ... portable code. ... Don't mess around with the Windows API. ...
    (comp.programming)
  • Re: Blocking read() policy?
    ... >> then it will perform bad on any platform including Windows. ... well designed applications on the other, provided you invest time in the ... Writing portable code from the beginning pays off big time. ... memory primitives, network I/O, file and directory code, low-level timing ...
    (comp.os.linux.development.system)
  • Re: Opinion) Overuse of symbolic constants
    ... > In portable code, the file names are specified by the user. ... sense to use something that's not going to confuse the user; ... Windows, that means using '\\' rather than '/' as the path separator. ...
    (comp.lang.c)
  • Re: Threading on Win32 - at an impasse
    ... > It's a pretty good guide in general when trying to write portable code ... > between Windows and Unix. ...
    (comp.lang.ruby)