|
|
Christopher James Huff wrote:
> In article <172### [at] 3-enet>, Daniel Matthews <dan#@3-e.net>
> wrote:
>
>> Thanks for that, it gave me a useful insight into POV's internals.
>> It also made me wonder if in some future version of POV the parser could
>> be data driven from an XML file so that it was extensible without having
>> to recompile. The XML file would supply the token information and a
>> reference to a loadable object or plug-in.
>
> This has the same problem as any other plug-in idea, it is platform
> dependant. You can't dynamically load code in a platform independant
> way, and the plugins would only work for the platform they are compiled
> on. If you could, you wouldn't need the XML representation of the syntax.
>
Oh, I see, but how does some Linux multimedia software such as mplayer uses
Windows codecs to decode and encode Video and Audio files?
--
Your connection failed because: Mail server hit by UniSpammer.
Post a reply to this message
|
|