First off, thanks for the response. I know your time is limited between all the forum posts.
Because we use a single language in our day work and we don't care for the others much. Is this enough for a reason?
Yes, it is reason, more than enough reason in fact.
Expecting that we'll start doing changes to our SDK (without a specific requirements) in order to support random/every language is optimistic.
At the moment I am just handling the idea. As for my self I havent invested in any expectation at all for your part. However, I am already starting to visualize how to implement it. The difference may be sutble, but I apologize if I sound or read as arrogant.
If you have a favourite language that is not supported you can:
1. look at the C::B's code
2. start making changes, so the support is improved or possible.
3. post a patch or better series of patches
4. fix reported problems and don't be afraid of criticism
Yes, I can agree to that being a proper way to proceed. Unless the idea is a little different than that. I am not talking about adding one language at a time, but to add ANY language in one single step. I want to synchronize with you all about this. But I am not going to do anything if my idea is not supported, right? However, I am willing to create all of the low level code for this, how does that sound? But, you are the core developers. I must know that once the low level code is created, that you will implement it somehow, by way of a single plugin or two or in any way. If there is no relatively covering consensus about this, the question is if I really should go about on this.
Sure, when I say in one single step, I am talking pretty big strides.
Do you think that it would be possible to do something like:
5. Create some of the "low level" code as a showcase to give you the idea of the concept?
Not that I am on my way to do any such horrendously stupid thing yet...
But if that be an option to proceed?