Jump to content

Bill Meyer

Members
 View Profile  See their activity

  • Content Count

    652

  • Joined

  • Last visited

  • Days Won

    12

Posts posted by Bill Meyer

  3. Posted

    Quite a few years ago, Jack Crenshaw wrote a series of articles on how to build a simple compiler. He wrote in TP, and develops the whole thing step by step. It is a recursive descent compiler, and originally emitted assembly code for a Motorola 68000. The articles have been further developed over the years, and the target altered to the 80x86. The value is simply that he wrote this for people who are not writing a compiler professionally, but who wish to learn the mechanics of compiling code. The writing is clear, and the whole development easy to follow. The articles can be found here:

    http://www.pp4s.co.uk/main/tu-trans-comp-jc-intro.html

     

    • Thanks 1

  4. Posted

    3 hours ago, KodeZwerg said:

    Does the code not work?

    Which code? You posted code for use in a package. I am now scanning the registry, and collecting from there with my own code, which works fine, though there are a few idiosyncrasies in the lists there.

     

    The  point of my last post, though, was that although the registry scan is convenient, it is specific right now to XE7. And given the minor irregularities I have found in the entries there, it seems reasonable to anticipate irregularities in other versions, whether the same or different to these. In D2007, however, I find no evidence of installed components in the registry, so in the end, the ToolsAPI may be the only reliable approach.

  5. Posted

    On 11/16/2018 at 4:16 PM, Uwe Raabe said:

    You can also search the registry. The Package Cache key (like HKEY_CURRENT_USER\Software\Embarcadero\BDS\19.0\Package Cache) contains all installed packages with all its components.

    As it happens, I need to run in XE7, where the key is this: HKEY_CURRENT_USER\Software\Embarcadero\BDS\15.0\ToolForm\Mapping. I also have an interest, though no absolute need, to run this in D2007, but I find no entry in the registry for such information. Has anyone committed a web page on the variations of such content in different versions?

  7. Posted

    In the course of some project analysis, it has become apparent that we would benefit from exporting a list of all installed components in Delphi. I have found articles discussing how to obtain the list using the ToolsAPI, but that would mean building a package for a wizard, which is more of a side project than I was seeking.

     

    If anyone knows of an existing wizard which would provide the functionality, I would appreciate a lead.

     

    Bill

  10. Posted

    Looks nice! Now, on a more serious note, I am dragging a very large app forward in time (from D2007), and trying also to untangle snarls of legacy sins. Bringing code into XE7 has been a necessary first step, and has shown me just how easily the IDE's internal systems can be compromised. Killing and restarting the IDE a few times an hour is annoying. So are the Out of Memory error. I freely grant that many issues are caused by poorly written code, but the rework can only be accomplished if a stable environment is available. 

    One example is the minor editing of an interface uses clause which all by itself provoked a rising memory burden until it was necessary to kill and restart. In a few cases, I found it easier to simply use Notepad++ to edit the file, and then reopen in Delphi.

    All versions work fine on small apps. But large apps filled with legacy code are an everyday reality.

  14. Posted

    Good info. I am on the verge of tangling with that beast, and am glad I won't have to find my way to that approach on my own. 

     

    I know  the DevExpress components are well liked, but I find a good deal of their stuff to be overly complex. And the documentation seems only to be reference material, not introductory and tutorial. Facing a 4,500 page reference manual is a lot like having no docs at all.

×