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

I am sure you are right about mixing languages being common. My exposure to that is limited though so I am trying to get a feeling of what the trade-offs would be. You are right too about wanting to avoid getting language drivers stuck at particular versions. This happened with the tool I referred to, although customers often believed getting stuck with a language version was an avoidable mistake by the manufacturers. For example, instead the framework could settle for organising code into integration classes without actually generating statements - i.e. one should abstract only what needs to be abstracted for maintainability.

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 14, 2015 at 09:38 UTC
It's worth adding that while mixing languages may be common, it's not necessarily maintainable unless done cleanly, e.g. using templates or at least having clear boundaries between the two languages in the source code. In the wild you'll see code like this all the time: `print "<span style=\"font-weight:bold;\" onClick=\"alert('bar!');\">";`	[reply] [d/l]