Re: Multithread safety

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



>
> See my previous reply. I'd start with writing small clients and servers
> using plain APIs. Then use other people libraries. Only when you know how
to
> use them and get a feel of what you don't like in them you should try to
> write a library of your own.
>

You were of great help,
Thank you very much !

Mike


.



Relevant Pages

  • Re: Converting a Win32_SecurityDescriptor to a SECURITY_DESCRIPTOR
    ... As regards the isolation of COM and WMI, I can only assume you haven't ... written many libraries, because sequestering a particular technology behind ... an abstraction layer is extremely common, and has the benefit of not forcing ... your clients to bring into their projects many, ...
    (microsoft.public.win32.programmer.wmi)
  • Re: Handling Bugs
    ... Frank Wagner ... Just so everyone knows, I always compile my database regularly, and also ... You still have to guarantee that all referenced libraries ... different clients insisted on their own idea ...
    (microsoft.public.access.formscoding)
  • Re: OO Concepts and C# Properties
    ... Shouldn't the object clients of the class vote on its interface? ... generic published libraries where the remote clients are assumed to have a ... And if nobody needs gets or sets, ...
    (comp.object)
  • Re: GUI libraries for C (not C++)
    ... provide POSIX compatibilities to otherwise non-compliant OSes. ... these sorts of libraries because of their functionality. ... Some on clc would never be seen on clcl. ... Many news servers will have already culled articles cross-posted to 8 ...
    (comp.lang.c)
  • Re: part 21 asserts forth best for small memory systems, would lisp be better in non small mem?
    ... libraries, servers, and applications alike ... ... Libraries: FSL, TOOLBELT, shuttlepad string handling (don't ask and I ... Servers: ThePanel text-driven fullscreen interactive user interface ... from simple FACILITY through to a rich ...
    (comp.lang.forth)