![](/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) |
>>> Sweet. I haven't taken the time to figure out how they unify the
>>> functional with all the stateful OO libraries.
>>
>> The real world is stateful. Almost all functional languages must have
>> a strategy for dealing with real-world state. Just apply the same
>> technique (whatever it is) to dealing with stateful APIs.
>
> Well, yes, except I suspect that's not how F# does it. :-)
I haven't researched it yet, but I suspect you'll find it *is* how it
does it. ;-)
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/15/2009 3:18 AM, Invisible wrote:
> What's the PlatformSDK?
Actually, it's called Windows SDK, now ...
--
~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) |
>> What's the PlatformSDK?
>
> Actually, it's called Windows SDK, now ...
Oh, OK.
So... presumably it's a big box full of header files and so forth?
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) |
>> Actually, it's called Windows SDK, now ...
>
> Oh, OK.
>
> So... presumably it's a big box full of header files and so forth?
"The Microsoft Windows SDK (Software Development Kit) is a software
development kit from Microsoft that contains header files, libraries,
samples, documentation and tools utilizing the APIs required to develop
applications" ... "The package contains an extensive documentation and
nearly 1000 samples."
http://en.wikipedia.org/wiki/Microsoft_Windows_SDK
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) |
> "The Microsoft Windows SDK (Software Development Kit) is a software
> development kit from Microsoft that contains header files, libraries,
> samples, documentation and tools utilizing the APIs required to develop
> applications" ... "The package contains an extensive documentation and
> nearly 1000 samples."
>
> http://en.wikipedia.org/wiki/Microsoft_Windows_SDK
OK, that sounds like the puppy then...
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) |
> OK, that sounds like the puppy then...
More like beast than puppy :-)
BTW I have wincodec.h on my machine, must have been installed as part of
MSVS C++ or something.
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:
> As far as I can tell, a *.COM file is just a file containing raw machine
> code. You load the entire file into memory, starting at a predefined
> base address [I forget what that is],
Remember 'org 100h'?
and jump to byte 0. And that's all
> there is to it.
And the reason I love them :-)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |