On Thursday, 27 March 2014 at 07:32:38 UTC, Mike Parker wrote: > On 3/27/2014 10:57 AM, FrankLike wrote: >> On Wednesday, 26 March 2014 at 10:42:09 UTC, Andrej Mitrovic wrote: >>> On 3/26/14, FrankLike <1150015857@qq.com> wrote: >>>> If you are programming on win32,now,DFL can be used by D2.065. >>>> Please git clone >>>> Open the folder w32 ->dflexe double click the 'makedflexe.bat' If you are programming on win32,now,DFL can be used by D2.065.Please git clone http:// github.com/ FrankLike/dfl Open the folder w32 ->dflexe double click the 'makedflexe.bat' >>> >>> FYI: you've changed one hardcoded path to another. I also don't >>> understand the removal of the package module. Anywho I don't use DFL >>> much. :> On 3/26/14, FrankLike <1150015857@qq.com> wrote:FYI: you've changed one hardcoded path to another. I also don'tunderstand the removal of the package module. Anywho I don't use DFLmuch. :> >> >> package module Let the all.d is null,most of codes have used the >> dfl.all,so keep all.d and remove package.d ,that's ok. >> >> thank you. On Wednesday, 26 March 2014 at 10:42:09 UTC, Andrej Mitrovic wrote:package module Let the all.d is null,most of codes have used thedfl.all,so keep all.d and remove package.d ,that's ok.thank you. > > It's fine to keep both. Old code (if any of it out there still compiles) can continue to use dfl.all, while new projects can make user of the newer package.d. The *.all technique should be deprecated in old projects like this, IMO, not encouraged. On 3/27/2014 10:57 AM, FrankLike wrote:It's fine to keep both. Old code (if any of it out there still compiles) can continue to use dfl.all, while new projects can make user of the newer package.d. The *.all technique should be deprecated in old projects like this, IMO, not encouraged.