100 said:
I'll try one more time. Like it or not the most of the software companies
are situated in North America And in those companies most of the programmers
doesn't have english as a first language. And they don't think in English.
Did you mean to write that most software companies are *not* situated
in North America?
(I hasten to add that *I'm* not situated in North America too, by the
way.)
I'm quite happy to agree that most software engineers don't have
English as their first language. That's why I've asked whether/which
other languages have preferences like this.
Try harder, Jon. I don't understand everything of your perfect anglish,
neither. I'm keep trying, though. Some times it takes me several times to
read one paragraph, but I never give up. I appreciate everything that you
say.
And the last I mean it.
Thanks - that's much appreciated. Feel free to ask for further
clarification on anything I say.
Hmmm. I prefer a programming language for expressing comparitions in my
programs. And I don't try to read it *out loud* in english it doesn't make
sense to me. I read it in C#, C/C++ or whatever language I use.
I don't read it *literally* out loud, but I do "sound it out" in my
head, with appropriate translations for symbols etc. I don't know how
many other people do that. It may well be because that's the way I read
(and write) natural language too. In my head, I'm currently "hearing"
every word I'm typing.
I have worked like that for a long time. And I'm wondering if you need to
write something in Perl let say. How can you manage to read it *out loud* in
english.
Using appropriate mental translations. The translation doesn't
necessarily always keep absolutely all of the context, either - when
you end up in a situation with lots of casting etc, a lot of the
context goes, but you can always get that back by careful examination.
Have you ever written programs in C++?
Yes, some. Not vast amounts - I've written rather more C than C++, and
it amazes me every (rare) time I have to go back to it just how painful
it is to allocate and free memory all over the place.
In C++ I found similar but significantly diminished problems - it was
fine when it was absolutely obvious who "owned" a bit of memory, but
that wasn't always the case. I'll readily concede that I'm really only
a novice in C++.
I suppose you have. I don't thing the
GC is the biggest advantage in languages like c# and Java. It sounds more
like commercial. I dare to say that I've never seen a question in a c++
group "How to free the memory".
Sure - but that's because all C++ programmers are going to know how to
do that because you absolutely have to.
There is a lot of questions about GC, though. And memory leaks in .NET.
There are lots of questions about how to free/delete objects in .NET
because people assume they have to if they've come from a C/C++
background. Yes, there are questions about the operation of the GC,
because it's a reasonably complex thing - but I still believe it saves
a *heck* of a lot of developer time compared with mechanisms in C/C++.
Why not when I don't need them anymore.
Because working that out in a deterministic fashion is basically
infeasible in any reasonable and robust way. There's a URL I can dig
out for you which gives some of the problems, if you want.
I preffer to have control on that
instead of use *dispose design pattern*, which looks more like a patch.
But why do you care when memory is reclaimed?
Take a look at some North American companies. You can find Indians,
Russians, English, Polish, Chinees, you name it programmers working together
in one team and doing great job.
Do any of them not understand English though? I suspect you won't find
many US programmers who don't use English in their code, even if it's
not their first language for speaking.
I think MS is such a company.
There is no problem with the language and no one of them speaks english like
you.
I suspect all of them can communicate in English though, and I suspect
that that's the language they use for documentation, method naming etc.
So, If you can't work with programmers, which you hardly understand without
making any effort the problem is entirely in you.
I'm willing to make an effort, but if we literally didn't have any
language in common at all, I don't believe it would be a productive
relationship. It would be insane to have to consult a dictionary every
time either "side" wished to use a class that the other "side" had
written. Like it or not, English *is* the basic lingua franca of the
Net and of programming in general. In my experience, even companies who
aren't based in the US/UK/Australia tend to produce APIs in English,
regardless of how they document internally.
Can you name any significant international open source efforts which
have their primary documentation and API naming scheme in a language
other than English, for example?