Skip to content
  1. Feb 26, 2002
  2. Feb 25, 2002
  3. Feb 22, 2002
  4. Feb 21, 2002
  5. Feb 19, 2002
  6. Feb 18, 2002
  7. Feb 15, 2002
  8. Feb 13, 2002
  9. Feb 11, 2002
  10. Feb 09, 2002
  11. Feb 08, 2002
  12. Feb 06, 2002
  13. Feb 05, 2002
  14. Feb 04, 2002
  15. Feb 02, 2002
  16. Feb 01, 2002
  17. Jan 31, 2002
  18. Jan 27, 2002
  19. Jan 25, 2002
  20. Jan 24, 2002
  21. Jan 22, 2002
  22. Jan 21, 2002
    • William A. Rowe Jr's avatar
      · c15460db
      William A. Rowe Jr authored
        Per W. Stoddard, Greg Marr and my research, let's get this right.
      
        This change is a decorative NOOP.  It accurately reflects what the
        MSVC compiler actuall turned into bytecode.  We hope this change
        makes the actual fns clearer to the developer.
      
        However, there is no effective difference.  The _stdcall declaration
        for these functions was _ignored_ by MSVC, which treated the fn's
        as _cdecl (our API_EXPORT_NONSTD macro) because they use varargs.
      
        This time, buff.c:ap_bvputs() was out of sync (correct to this patch)
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@92965 13f79535-47bb-0310-9956-ffa450edef68
      c15460db
    • William A. Rowe Jr's avatar
      · a944e9f4
      William A. Rowe Jr authored
        ap_rprintf is implemented as API_EXPORT() in http_protocol.c.
        Therefore, make the prototype and implementation consistant.
      
        The question remains, why no compiler warning/emit?  Because MSVC [my
        version, at least] must have changed all of the ap_fn(foo, ...) decl
        from _stdcall to _cdecl, on it's own!
      
        I suggest our declarations are still borked, but they have worked only
        because MSVC ignored our poor judgement :)
      
      
      git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@92964 13f79535-47bb-0310-9956-ffa450edef68
      a944e9f4