in reply to Re: Maximising Language integration: Holy Grail or Dystopia?
in thread Maximising Language integration: Holy Grail or Dystopia?

I have a bit of a chicken and egg problem here. If I could write such examples, I'd have answered my own question and could just go ahead and build the classes to support the examples. My hindrance is that I am still struggling with some fundamental decisions. The most promising is to code a web page in Perl as a list of nested objects to match XML structure, each of which may have hooks into database tables, CSS and javascript routines. The support for transferring the inline code into separate sources for each language could be achieved by multiple inheritance. One of the challenges is where to draw the line between declarative and procedural code. One of the concerns is ... would I be re-inventing Template Toolkit?

One world, one people

  • Comment on Re^2: Maximising Language integration: Holy Grail or Dystopia?

Replies are listed 'Best First'.
Re^3: Maximising Language integration: Holy Grail or Dystopia?
by Anonymous Monk on Jul 15, 2015 at 12:01 UTC

    The point was a little more basic than that: You're talking in quite broad strokes with abstract terms, and I don't completely understand the question. You're not going to find a silver bullet anyway, so if you want more pragmatic suggestions, we'll need to know more about the problem space (how big is the software project you are looking at, what technologies does it involve, etc.). The request for sample code was not asking for an example of the solution, it meant show us the problem you are trying to solve.

      The question put more succinctly is: I am considering creating a Perl class (with some parents it needs) to service conceptual objects that get implemented as objects in different languages in different sources. The intention is to support multiple frameworks and even multiple meta-frameworks such as bootstrap. Or is this pointless and I should just accept the multi-language style and not try to integrate.

      One world, one people

        The point was already made that you'll need to write tests for your code, make sure it's maintainable, and that the maintenence does in fact happen as long as the code is in use. My experience has been that test & maintenance usually create more work than it would have been to use an existing language / tool / framework. But if you think your case is manageable, then feel free to write your tool :-)