Printable View
Of course, once you work out and profile that a part of your code is too slow and you're pretty sure your algorith is the fastest, then one should recode the module in C or assembler and link to that code in the time saved by using C# over writing the whole project in assembler. :)
That would be embedded software - I'd wager there's more embedded software in the world than PC software. It's got a whole other set of requirements - you don't have a gig of ram and a 30 bazillion GHz processor to do fun stuff with. That's why C will be a very long time in dying. It's got a relatively clear and popular syntax, it's reasonably efficient, it allows low-level memory manipulation, and still allows for good OOP-style design (although without language support). Remember - the right language for the right job!Quote:
Originally posted by vma
I am working for an automotive company and I do the tool support. Of course that using C# is the best way to achive good results in little time and as the others say it quite fun. But working here it shows me what the others programmers are doing for car's ECU's (Electronic Control Unit). For the ones that are not familiar whit automotive I can say than now even the spark for a car's spark plug is given by a software. This you will not do in C# now and I think that you will not do it in c# in the near future even.
indeed - if i was feeling british i'd say 'here here !'.
but with Bush being here ....
:(
When you benchmark, make sure you do two separate benchmarks on your C# code (or any other .NET code). Benchmark the code running it the first time, then benchmark it separately after having ran all of the code once. With the JITs in the runtimes, you should only take a real performance hit the first time code is ran. (JIT=Just in Time compiler)Quote:
When I get time i will benchmark my rank/hash functions from native c++ to C#, and post the results. A little tweaking in the .Net core and i would be happy
Just a thought.
On another note, someone mentioned decompiling. If you value your source/logic, then you will obfusicate any publicly released .NET programs.
Brad!