I'm sure there are fine points of difference. The bit about the
interface not being checked against the actual procedure might be one of
those; I'm not actually C/C++ fluent enough to be sure of points at that
level of detail.
In C et al., you include the interface definition file (.h file) not only
for a reference, but also in the implementation body. This gives the com-
piler a chance to check the interface definition against the actual imple-
mentation at the proper place.
For F90, I have always viewed explicit interfaces as a crutch catering to
the fact that many programmers will have access to pre-F90 compiled (libra-
ry) code whose interfaces are documented on paper only, with no access to
the source code. In these cases, it is a one-off work item to write the
explicit interfaces and check them against the docs and (hopefully) also
the implementation, and then providing similar security of use from then
on. OTOH, for code to which one has access to the source and/or whose inter-
faces are actually moving targets, modules are a much better solution.
Re: Extending ATL COM Object Dual Interfaces ... providing you have the source code.... > I have a need to extend existing CoClass functionality with dual ... the CoClass must contain dual interfaces to ... > support scripting clients as well as vTable support for early binding. ... (microsoft.public.vc.atl)
Re: Fedora Desktop future- RedHat moves ... I could have gotten a copy of the source code that it's own author and the experts involved in the OS packaging couldn't fix. ... But if you walk away from your interfaces particularly without supplying replacements for the things that will break, no one can be expected to trust you. ... I do recall reading about some issues with firewire but never ... (Fedora)
Re: CLR details- Are MSCorEE.dll and MSCorWks.dllMSCorSvr.dll COM ... I'm having a source code license and I'm not interested ... Also tlb files do not ... necessarily represent accurately the COM interfaces of a COM server, ... (microsoft.public.dotnet.framework.clr)
Re: [PATCH] char: Add Dell Systems Management Base driver ... > systems management software that access the interfaces are ... > source code for the software. ... > following Dell proprietary hardware systems management interfaces:... (Linux-Kernel)
Re: One good argument against using "with" ... Is there any reason those interfaces couln't be made TPersistent... not possible to re-generate the source code using these interfaces. ... It also has a Descendants property.... (borland.public.delphi.non-technical)
