[Issue 2370] Version statement enhancement: versioned identifiers

d-bugmail at puremagic.com d-bugmail at puremagic.com
Thu Oct 9 05:22:20 PDT 2008


http://d.puremagic.com/issues/show_bug.cgi?id=2370


snake.scaly at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alan at akbkhome.com




------- Comment #11 from snake.scaly at gmail.com  2008-10-09 07:22 -------
(In reply to comment #10)
> (In reply to comment #0)
> why do you think that code working for d2 will work for d3?

It's my best guess that D3 will likely support D2 way of doing things rather
than D1, if at all.  If I'm wrong I'll fix my version statement to support
whatever D3 requires.  But if I'm right I won't be needing to change anything.

Note that D version is only an example.  This sort of version compatibility is
required when you need to support multiple versions of a library or a host
application.  If I write a plug-in for 3dsmax that must support versions 8, 9,
2008, 2009 and as many future versions as possible, and I know that a
particular API is only available from 9 onwards, I put its use under
version(max,9) and hope that 2010 will support it as well.


-- 



More information about the Digitalmars-d-bugs mailing list