Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

ReportBuilder errors under Delphi 2009

edited November 2008 in General
Hello !

Delphi 2009 error references when attempting to run application:

[DCC Warning] ppSynUEditWordWrap.pas(221): W1047 Unsafe code 'FreeMem'
[DCC Warning] ppSynUEditWordWrap.pas(222): W1047 Unsafe code 'FreeMem'
[DCC Warning] ppSynUEditWordWrap.pas(285): W1047 Unsafe code 'ReallocMem'
[DCC Warning] ppSynUEditWordWrap.pas(298): W1047 Unsafe code 'ReallocMem'
[DCC Warning] ppSynUEditWordWrap.pas(460): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(464): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(472): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(485): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(493): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(541): W1047 Unsafe code 'FreeMem'
[DCC Warning] ppSynUEditWordWrap.pas(581): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(585): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(593): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(606): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(614): W1047 Unsafe code '^ operator'
[DCC Warning] ppSynUEditWordWrap.pas(652): W1047 Unsafe code 'ReallocMem'
[DCC Warning] ppSynUEditWordWrap.pas(654): W1047 Unsafe code 'ReallocMem'

Comments

  • edited November 2008
    Hi Richard,

    These are compiler warnings and should not affect your application. Are you
    able to successfully run your app in Delphi 2009?

    We generally turn the Unsafe Code, Unsafe Typecast and Unsafe Type warnings
    off due to the fact that they can appear for correct code and they tent to
    slow the compile and build time.

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited November 2008


    The intent of the 'Unsafe' warnings is to assist developers preparing code
    for VCL.NET. In the managed code world the use of memory allocation and
    pointers is considered 'Unsafe'. And while it is a good practice to limit
    such operations, it is often necessary to interact with the Win API.

    By default those warnings are usually turned off and by default your
    projects usually compile against RBuilder\Lib. However if you turn those
    warnings on and add RBuilder\Source to your library path, then they will
    appear.


    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited November 2008
    > The intent of the 'Unsafe' warnings is to assist developers preparing code

    maybe I misunderstood, but isn't VCL.NET dead with Prism?

    Ed Dressel
  • edited November 2008

    Correct. VCL.NET is dead.

    Those compiler warnings were introduced in Delphi 7 to help developers
    prepare their code for the first version of VCL.NET.


    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.