![]() |
|
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 |
|
Programmer
|
What is the quickest language?
What is the quickest programming language at manipulating arrays and comparing them. I've assumed its Assembly since theres not very much going on that you don't know about, so theres no unnecassary actions going on. But am I right, since I really don't know much about assembly and other languages. I know Delphi is really fast (From my standpoint)... anyways, hopefully somebody can help me out. G'day everybody
, and sorry for bothering you again with another nooby question ![]() |
|
|
|
|
|
#2 |
|
Resident Grouch
![]() ![]() ![]() ![]() ![]() ![]() Join Date: Jun 2005
Posts: 6,453
Rep Power: 10
![]() |
Well, whether or not there are unnecessary actions depends upon your skill. Stripped down assembler instructions would be the fastest, properly implemented. The lack of "other things going on", such as calls to introduce modularity, could be more damaging than beneficial, though. It's a prime mistake to worry about optimization before you know what you're doing. It's very easy to blow scads of effort for no real result.
Learn programming, assembler if you like, then learn the more abstruse elements of efficiency.
__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers |
|
|
|
|
|
#3 |
|
Programmer
|
Ok, thanks
. I was just wondering if assembler was somehow slow compared to other languages, though I seriously doubted it. But when I first started programming and got into Batch (Found that changing the extension to .Bat has some interesting results , hehe) I never knew I was moving at a snails pace compared to other languages. Anyways, thanks for the quick response, I'll try to learn Assembler as best I can then I can try to do what I've been aiming for, g'day m8 ![]() |
|
|
|
|
|
#4 |
|
Resident Grouch
![]() ![]() ![]() ![]() ![]() ![]() Join Date: Jun 2005
Posts: 6,453
Rep Power: 10
![]() |
Bub, all languages ultimately emit machine code; assembler is a mnemonic reference (generally speaking) for that code, so it's as close as you get without writing numbers. Interpreters, VMs, native code, it doesn't matter -- it eventually gets shoved at the machine as machine code. That's all it understands. Some reading seems to be in order.
__________________
Abstraction doesn't make it impossible to write bad code; it makes it possible to write superior code. Contributor's Corner: Grumpy on C++ Exceptions DaWei on Pointers |
|
|
|
|
|
#5 |
|
Programming Guru
![]() Join Date: Aug 2005
Location: England
Posts: 1,499
Rep Power: 4
![]() |
Google do a lot of work with large sets of data, and they use C++. Beyond a certain point, the disadvantages start outweighing the advantages. I shouldn't think that you could get much gains in assembly over C. Unless you're working with very low resources (such as a PIC or some small, embedded system), I shouldn't think assembly would be your best choice.
|
|
|
|
|
|
#6 |
|
Programmer
|
DaWei, I knew that part
, hehe. And Arevos, thanks , I'll probably take your advice and go with C or C++. G'day all, and thanks for the help ![]() |
|
|
|
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|