search

fpjohnston / TECO-64

Enhanced and portable version of TECO text editor in C.
24 stars 6 forks source link

Added support for Xalan-C #3

Closed polluks closed 2 years ago

polluks commented 2 years ago

The Java and the C implementation use incompatible command arguments, stupid.

fpjohnston commented 2 years ago
  1. Do you need support for both the C++ and Java versions? The Java version looks rather old.
  2. Do you need to make changes to the XML or XSLT files? That's not normally required to build TECO.
  3. What are you trying to communicate by calling someone stupid?
polluks commented 2 years ago
  1. No, just your own personal preference.
  2. No, it worked out of the box.
  3. Well, everybody should pay attention to compatibility IMHO.
fpjohnston commented 2 years ago

Given that the XML/XSLT files are not required to build TECO out of the box, as you confirmed, I don't know why I should have anticipated that someone might have used a different xalan executable than I did.

As for compatibility, I'm willing to make and in fact have made numerous enhancements, fixes, and other changes after receiving feedback from users. But I'm only one guy, and this isn't my day job. And I'm rather disinclined to acquiesce to requests from anyone who expects to motivate me by being rude. I certainly don't think I'm obliged to try to ensure in advance that my software will run in environments I've never used.

So, would you care to rephrase your original comment?

fpjohnston commented 2 years ago

The TECO distribution includes all required header files, so it should not be necessary to rebuild any of them with xalan, let alone for the makefile to anticipate alternate versions of xalan. If such an alternate is required in a particular environment, custom modifications to the makefile can be made there to accommodate it.

And, please note that while the copyright notice states that TECO is provided free of charge, it also states that there is no warranty pertaining to its fitness for any particular purpose. This includes its use on platforms, in environments, or with tools, where it has not been specifically tested. And while additional support may be considered in the future, any requests for such should bear in mind the desirability of maintaining a civil discourse.