>>> All we need now is for Warp to pop up and tell me that if only I used 
>>> a *real* programming environment like VisualStudio C++, I would only 
>>> need to click on a button and everything would instantly work right...
>>
>> Or Scott to pop up and tell you to just use a .net language and be 
>> done with COM altogether.
> 
> Or both! Use a .NET language and tell it to interface itself to COM. ;-)

What a wonderful idea! Instead of having a compiled Haskell program that 
requires you to install 10MB of GTK+ libraries before it will run, you 
can have an interpretted .NET program which requires you to install 
400MB of libraries before it will run. Everybody wins...

>> http://www.ffconsultancy.com/dotnet/fsharp/rule30/code/1/rule30.fs
> 
> 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.

The tricky part is usually the type system...

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Orchid XP v8 wrote:
> can have an interpretted .NET program 

.NET isn't interpreted.

>> 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. :-)

-- 
   Darren New, San Diego CA, USA (PST)
   I ordered stamps from Zazzle that read "Place Stamp Here".

Post a reply to this message

>> ...in order to use it, you need to include the header file wincodec.h
>> (which I don't have), and you need to link in windowscodec.lib (which I
>> also don't have). It seems almost pointless to continue reading about
>> the API, because I can't actually call it anyway.
> 
> You probably will need to download the latest PlatformSDK from 
> Microsoft. That will contain all of the windows components you need, 
> even stuff to interface with Vista and Windows 7!

What's the PlatformSDK?

Post a reply to this message

>>> 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

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

>> 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

>> 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

> "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

> 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

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