in reply to Re: Re: Re: The classical TAB issue
in thread The classical TAB issue

My iPAQ still has only 64MB RAM and 16MB Flash. And my mobile phone just only 4MB RAM.
  • Comment on Re: Re: Re: Re: The classical TAB issue

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: The classical TAB issue
by hardburn (Abbot) on Apr 07, 2004 at 16:21 UTC

    Do you write programs for either of those? If you do, do you use a langauge that would be compiled (either to machine code or to bytecode that is stored in a seperate file)? In either case, using tabs vs. spaces is still irrelevent from a file size point of view.

    ----
    : () { :|:& };:

    Note: All code is untested, unless otherwise stated

      I use and write Perl and Perl/Tk programs for my iPAQ/Linux PDA. To save space, I sent the whole Perl/Tk distribution through perltidy with the option to remove Pod, comments and unnecessary whitespace.
Re: Re: Re: Re: Re: The classical TAB issue
by hossman (Prior) on Apr 07, 2004 at 17:35 UTC

    I was refering to code you are editing -- if you then want to install/run that code on a device where size is important, then there's all sorts of things you can do to help save bytes, even in an interpreted language. space->tabs may save some space, but converting all insignificant whitespace into single spaces is even better, and converting variable names to single characters can save a tone more.

    Of course, if you're acctually editing source code on your iPod and Cell-Phone, then my point is void, and I weep for you.

      Of course, if you're acctually editing source code on your iPod and Cell-Phone, then my point is void, and I weep for you.

      Ocassionaly I do (mostly for quick fixes) and it is no fun :-)