Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Doing it wrong? (Score 1) 600

Unless you write code directly in assembly, the stack is far from what you "the hardware stack".

A recursive algorithm use the function call stack and the translation of that stack to the CPU stack is dependent on the compiler or the runtime environment. The limits of that stack is also dependent on the runtime environment, and the program may even have control of the size of that stack at runtime to raise the limits if necessary. The OS may also give control to the OS user on the size of that stack (man setrlimit) outside of your program (the program exhausts the stack? run again with a higher "ulimit -s").

Computer resources (not just the stack) are always limited anyway. Using one algorithm or another is always a tradeoff on which resource you may exhaust first. The stack size is not always the first exhausted resource for a recursive algorithm. So "Never use recursion" should not be general rule.

Unrolling a recursive algorithm to loops also has a cost: the code is often longer (in lines of code) and more complex (because you have to maintain the state that is handled in the stack in the recursive case), so may be harder to maintain and may have more bugs. You'll often have to write unit tests that compare the correctness of the unrolled implementation against the (simpler) recursive one.

Comment Re: No. (Score 1) 435

In some countries, when you leave a job you get a statement of income to date for the tax year, which you then give to your next employer so they can set up the right deductions on your salary payments.

And so? How will they prove that they made you an offer based on a false oral statement from you? Because they recorded the interview? I don't think that would be legal.
In any case that would be little ground for a ligitation. If this subject comes in a court, you probably have a much bigger problem in your relationship with that employer.

Comment Re:GitHub? SourceForge? Other? (Score 1) 225

> The really relevant stuff doesn't need a url anyway, because they already know the name of the software.

The other obscure stuff is also helpful to the recruiter. At least to eleminate you if your side projects are just shit. If your side project made in your free, unlimited time is just badly coded, with poor commit messages, what can a recruiter expect from you code quality on a time-constrained project?

Comment This is achievable... for traffic in Russia (Score 1) 296

1. Scan all traffic at edges of the network in Russia.
2a. If you are able to decrypt it (well, if ever a implementable definition of "decrypt" is published), let it pass.
2b. If not, block it.

All the traffic that remains is decryptable. So this is achiveable, as long as you accept as a compromise to block so much traffic that not much usage of the Internet remains.

Slashdot Top Deals

Stinginess with privileges is kindness in disguise. -- Guide to VAX/VMS Security, Sep. 1984

Working...