I have started a new GitHub project. Something similar to JEDI.inc but oriented around 'features' (ERRTI, attributes, generics ...), not around compiler versions.

Comments

  1. Good Idea.
    Maybe you could add DelphiXX_UP defines, too? Sometimes you workaround a bug which is compiler/component specific for a specific version(and i doubt you want to add defines for each bug :D). So otherwhise you'd need this inc and another one to specify the delphi defines

    ReplyDelete
  2. Well, this project may die before it even started :) As Ollivier Sannier pointed on the FB, JEDI.INC (https://github.com/project-jedi/jedi/blob/master/jedi.inc) already contains HAS_XXXXXX and SUPPORTS_XXXXX defines inside, with much more complete list than mine!

    ReplyDelete
  3. Sorry,  but the first thing that this brings to mind is: https://xkcd.com/927/

    ReplyDelete
  4. Primož Gabrijelčič then keep in mind to remove it from Delphinus again if it dies ;)

    ReplyDelete
  5. Alexander Benikowski I have killed the repo, shouldn't that remove it from the Delphinus?

    ReplyDelete
  6. Mason Wheeler  The nice thing about standards is that there are so many from which to choose. ;)

    ReplyDelete
  7. Honestly I think it would be a good idea to put jedi.inc in it's own repo and rename it to something more generic like CompilerVersions.inc or something. It's one of the most useful things in the Jedi project. That's not to say the rest of the project is in any way useless. It's just that the conditionals defined in jedi.inc are useful to pretty much any project that needs to work with multiple versions of Delphi.

    I've seen jedi.inc copied all over the place. It'd be nice if developers could just add an svn:external or subrepo to their pet project to pull in the latest version and update whenever they need to.

    ReplyDelete
  8. Primož Gabrijelčič yes, the searchrequest returns without your repo, but the local cache is still there(which must be removed, that's a bug atm)

    ReplyDelete
  9. Kenneth Cochran Jedi.inc is in its own repo.

    ReplyDelete
  10. Stefan Glienke
    Wow, when did that happen?

    ReplyDelete
  11. Great work!
    That's exactly how it should have been from the beginning - checking against features, not version numbers.
    It's a real pain to update all the 3rd party packages that got abandoned by the original developer but are still used in our projects. In most cases it's just an modification of the compiler version checks.

    ReplyDelete

Post a Comment