Viktor Szakats 7c8fcec7f3 2012-11-29 01:20 UTC+0100 Viktor Szakats (harbour syenar.net)
* contrib/rddads/ads.ch
    ! added missing self-guard

  * contrib/hbmagic/tests/hbmagit.prg
  * contrib/hbmxml/tests/custom.prg
  * contrib/hbmxml/tests/reminder.prg
  * contrib/hbmxml/tests/testmxml.prg
    % no longer use #include to include standard
      package headers. Rely on autoload triggered
      by .hbc file or #require directive.
      (missed from prev)

  * contrib/rddads/tests/datad.prg
  * contrib/rddads/tests/testmg.prg
    ! fixed to run properly as scripts
      (need to register RDDs manually in such scenario,
      maybe this could be automatized?)

  * contrib/hbwin/hbwin.hbc
  * contrib/rddads/rddads.hbc
    + set hbwin.ch and ads.ch as standard headers

  ; NOTE: Seems that hbct, hbxpp and xhb contribs
          do not have such what could be called
          common standard headers.
          For gtwvg I cannot tell, but probably
          all three .ch files should be standard.

  * contrib/hbwin/tests/testax.prg
  * contrib/hbwin/tests/testcom1.prg
  * contrib/hbwin/tests/testcom2.prg
  * contrib/hbwin/tests/testcopy.prg
  * contrib/hbwin/tests/testevnt.prg
  * contrib/hbwin/tests/testgdi.prg
  * contrib/hbwin/tests/testmapi.prg
  * contrib/hbwin/tests/testprn.prg
  * contrib/hbwin/tests/testreg.prg
  * contrib/hbwin/tests/testsvc.prg
  * contrib/hbzebra/tests/testwin.prg
  * contrib/rddads/tests/datad.prg
  * contrib/rddads/tests/testmg.prg
    % no longer use #include to include standard
      package headers. Rely on autoload triggered
      by .hbc file or #require directive.

  ; WARNING: The autoload feature for standard package
             headers should be generally harmless, but
             it might as well pose an INCOMPATIBILITY
             if user code redefines or simply uses
             macro names/commands in user code that
             collide with the ones defined in these
             standard headers.
             If this comes up, avoid using .hbc files,
             until your code is changed/fixed to avoid
             name collisions either by renames or 
             undeffing the standard ones.
             As consequence it's even more important
             to pay attention to macro namespaces used
             in package headers to avoid accidental
             collision with user code. This was standard
             practice for function/class names, now it
             is extended for macros/user commands.
2012-11-29 00:30:07 +00:00
Description
Harbour Core — Reference source for Five development
172 MiB
Languages
C 80.3%
xBase 17.8%
Makefile 0.6%
C++ 0.4%
Harbour 0.4%
Other 0.3%