![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Darren New schrieb:
> Not necessarily. But I'm pretty sure you're not going to get good
> "globally unique identifiers" by manually including english words in them.
Well, if you /know/ you're the /only/ one stupid enough to do that... :-P
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Orchid XP v8 schrieb:
> Apparently it is notionally possible to construct a DLL which actually
> contains no executable code at all, only data. (Although I highly doubt
> anybody *does* this...)
I once actually did - for a collection of self-made icons I wanted to
have displayed for certain files in Windows Explorer.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Fredrik Eriksson wrote:
> An "interface" is a list of function pointers. In C and C++ the layout
> of an interface is typically described in a header file.
I see. So without the magic table that tells you the index of each
function pointer, you can't play with COM?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> Apparently it is notionally possible to construct a DLL which actually
>> contains no executable code at all, only data. (Although I highly
>> doubt anybody *does* this...)
>
> I once actually did - for a collection of self-made icons I wanted to
> have displayed for certain files in Windows Explorer.
Why not just have a bunch of .ico files?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 10/12/2009 10:34 AM, Invisible wrote:
> Well, in the case of VST, it's not that it's undocumented, just that you
> have to pay money for the documentation...
Naughty mascot. You don't have the license to create plugins. How much
is the SDK?
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>> Well, in the case of VST, it's not that it's undocumented, just that you
>> have to pay money for the documentation...
>
> Naughty mascot. You don't have the license to create plugins. How much
> is the SDK?
I just object to paying money for somebody to tell me the code numbers
of a set of functions, that's all.
for an envelope containing a sheet of paper with a number printed on it.
Like, WTF?)
It's not like I'm going to build a multi-million dollar software product
and not pay Steinburg. I'm only tinkering. ;-)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Tue, 13 Oct 2009 10:18:33 +0200, Invisible <voi### [at] dev null> wrote:
>> An "interface" is a list of function pointers. In C and C++ the layout
>> of an interface is typically described in a header file.
>
> I see. So without the magic table that tells you the index of each
> function pointer, you can't play with COM?
Pretty much.
Even if every function had been exposed directly in DLL export tables, you
would be no better off because you would still need to know the function
signatures. The bottom line is that you cannot reasonably expect to use an
interface (of any kind, not just COM) without documentation.
--
FE
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Fredrik Eriksson wrote:
> The bottom line is that you cannot reasonably
> expect to use an interface (of any kind, not just COM) without
> documentation.
Yeah, figures.
Oh well, dream on...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Invisible wrote:
>>> Apparently it is notionally possible to construct a DLL which
>>> actually contains no executable code at all, only data. (Although I
>>> highly doubt anybody *does* this...)
>>
>> I once actually did - for a collection of self-made icons I wanted to
>> have displayed for certain files in Windows Explorer.
>
> Why not just have a bunch of .ico files?
Because it would be a bunch of .ico files? lol Sort of the same reason
they make zipped files, or one sort or another, with games, for levels.
You just download/update *one* file, not dozens. Though, unlike dlls,
patchers will tend to use something similar to the "add to .zip/.rar"
function when updating things. Even windows uses icons in a dll, keeping
all the default ones in a single source file, which gets shown in cases
like where you have a file that doesn't have its own internal icon, and
you try to change the one being used.
But, yeah. I forgot that dlls can also just be sort of like resource
forks too.
--
void main () {
if version = "Vista" {
call slow_by_half();
call DRM_everything();
}
call functional_code();
}
else
call crash_windows();
}
<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
3D Content, and 3D Software at DAZ3D!</A>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> an envelope containing a sheet of paper with a number printed on it. Like,
> WTF?)
Hehe, we just paid about 4000 pounds for a 46 byte text file :-)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |