I am not able to login traditionally into my Ubuntu Linux, because the hard drive is full. How do I login into the command line, so that I can delete some files and free up some disk space?
When I attempt to log in, it bounces me back to the login screen.
Find and remove the files that are using up all your space and you should be able to log in again.
GL :-D
Quote :
I am not able to login traditionally into my Ubuntu Linux, because the hard drive is full. How do I login into the command line, so that I can delete some files and free up some disk space?
When I attempt to log in, it bounces me back to the login screen.
Well that would depend on the optimizer if the language uses one.
There are ways to hand-optimize code, but writing code like that is often done for other reasons. Performance is not usually a factor, although sometimes it helps.
:-D
Quote :
Would there be any much difference in execution speed? Is there any justification for single line monsters? I'll allow them for personal use perhaps..
Especially considering that perl is an interpreted language (meaning you don't create a self-runnable executable binary when you're done), it is difficult at best to optimize the stuff by arranging code in a specific way and rather it's just an exercise in using efficient calls and reusing results that garner the best improvements. Large, hard-to-read single lines are done usually for that purpose: to make it more obfuscated. It may also be done as a personal preference I suppose.
Also, as a C programmer, I feel it necessary to again denounce the evil that is perl. If I don't they take away my System Programmer card
But I must defend Perl and interpreted languages in general. There are many tasks they do very well. Perl, PHP and other languages can be great tools, it is up to the programmer to write proper code.
Naturally both Perl and PHP are written in C :-D
Quote :
Especially considering that perl is an interpreted language (meaning you don't create a self-runnable executable binary when you're done), it is difficult at best to optimize the stuff by arranging code in a specific way and rather it's just an exercise in using efficient calls and reusing results that garner the best improvements. Large, hard-to-read single lines are done usually for that purpose: to make it more obfuscated. It may also be done as a personal preference I suppose.
Also, as a C programmer, I feel it necessary to again denounce the evil that is perl. If I don't they take away my System Programmer card
lol.. I still remember all the good things Pascal used to force me to do when I did a bit of coding at Uni.
To my mind though truly optimised code would involve timing diagrams and a hex editor. Otherwise you are limited by the compiler / interpretation. At my level of skill at any language I played with I settled for including my flags at compile time...
Under normal circumstances a well written compiler should optimize a lot better than most human beings can.
In rare situations a true master of assembly language may be able to do a bit better, however few people know assembly these days and even fewer know how to write perfectly optimized assembly code.
I'm sure bmouring knows C and assembly a lot better than I do :-D
Maybe he can comment further.
Quote :
lol.. I still remember all the good things Pascal used to force me to do when I did a bit of coding at Uni.
To my mind though truly optimised code would involve timing diagrams and a hex editor. Otherwise you are limited by the compiler / interpretation. At my level of skill at any language I played with I settled for including my flags at compile time...
...
Under normal circumstances a well written compiler should optimize a lot better than most human beings can.
...
In many, many cases this is the absolute truth, however there are those specialized situations (usually a tight mathematical algo) that can be done best in assembly, hence the inline assembly capabilities of most compile-able languages.
Also, linux_0, you know my jabs at perl are all in good fun. I fully appreciate what perl can do and have even written a few system maintenance apps in it. It's just not usually my cup of tea.
@ bmouring I figured it was a friendly jab but sometimes after you've been up a few days straight you can't pick up on that :-D
Indeed, algorithms are in fact quite tricky, someone with a mastery or algorithms and mathematics could probably do a better job than the compiler could.
Of course some compilers optimize better than others and some compilers are known to de-optimize for certain architectures.
Quote :
...
Under normal circumstances a well written compiler should optimize a lot better than most human beings can.
...
In many, many cases this is the absolute truth, however there are those specialized situations (usually a tight mathematical algo) that can be done best in assembly, hence the inline assembly capabilities of most compile-able languages.
Also, linux_0, you know my jabs at perl are all in good fun. I fully appreciate what perl can do and have even written a few system maintenance apps in it. It's just not usually my cup of tea.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.