Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I got a project that is already developed, in other words I have an API for some software that coded in C language, but the company haven't the source code, thus my mission is to write the source code for this application. Now I have the executable program and I want to write the source code, regarding to my less experience I'm asking, which is better, to write the source code from the scratch or to use some reverse engineering tool to find out the source code? But notice that reverse engineering tools results with some hard to read files since there are not enough comments!
No reverse-engineering tool will give you a source code (with or without the comments). So you can safely abandon this idea.
It is definitely better (in your case) to write new code from scratch using the existing executable as your black-box reference point.
Make sure to have many test cases that should cover as much of the original functionality as possible and when you are done writing your code run them all to affirm that your code is a reasonable replica of the original.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
If I want to create a game in C with SDL for example, is there a reason of why I should use a scripting language like Lua with it (since alot of commercial games uses a scripting language)? I have heard that scripting languages often are faster to write and easier to read, but what should they do? (graphics? ai? input? etc).
They should interact with the various "programming primitives" that the native code implements. That is, the native code should only do enough to allow the scripts to function within the game (although "function" can sometimes mean speed-wise).
If that sounds cyclical... it is. There's no complete way to define at the beginning of development what responsibilities the native code will have as the project progresses.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was reading a ton of tutorials and wanted to get into GBA Homebrew
Now, should i use C or assembly? I already know a bit of C, but asm wouldnt be difficult to me, and i was interested in learning it anyways.
So, which one?
C is easier to develope, specially complex and long programs, and it will take you way less time than making it in assembly, plus you can write assembly in c. Assembly on the other hand can get you better performance if done correctly and it's more flexible.
So I would say go ahead with C
The general rule for the asm vs C no matter what platform (that has both choices) is to use C and only if you really have to use asm for performance or other reasons use asm...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am writing a dissertation for university final year.
I want to put a large amount of source code on a DVD for the appendix.
95% of code is written by me, but some code is copy and pasted from samples and taken from forums.
Do I have to label each bit of code that is not mine or something?
What would I write if I don't know who's code it is anymore?
You should definitely cite your source if the source specified you do so. However, if you are taking samples and adapting them to your environment you usually don't have to cite it (as long as it has changed in a significant way).
Usually, I try to include a comment in my code if I just copy and paste something, even if it is free and open to copy. However, this is more of a preference than a specification.
In the end, it is up to the people you got the code from (if they specified a license for the code) and your advisor at the university.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to understand how sqlite is implemented. And, want to read the source code( I have already downloaded the source). Which part of the code I should start looking at?
The SQLite documentation page has a great section named SQLite Technical/Design Documentation with articles on the internals of SQLite. I think it's essential to read and understand those before you start reading the source code itself.
There are many gems there, but the most interesting for you is probably Architecture of SQLite, as its description says:
An architectural overview of the
SQLite library, useful for those who
want to hack the code.
That page contains a nice block diagram of SQLite's code:
And then explains where in the source to find the implementation of each such block.
Another great resource (linked from here) is the Oreilly mini-book ("Short Cut") named "Inside SQLite" which goes into the design and code of SQLite to explain how it works.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
How would i licence my c command line program, e.g limited functionality without a serial number?
Depends what licensing means ...
Write the license text into the source code resp. show the license text when installing or starting the program.
If you want prevent users from copying the program, things get complicated, you might need some hardware dongle.
Or just make it GPL and give the source code away ...
Include a EULA (End User License Agreement) in your program which users will have to accept while installing/using your application. You can get lots of sample EULAs in Internet. Replace the Names appropriately. But remember, you are gonna do things at your own risk. Read the EULA well, modify it to suit your needs.