|
|
|||||||
Very minor but still... we've got @CRLF, can't we have @TAB too |
||||||||
|
|
|||||||
I vote against. I accept that some ppl didn't remember in which sequence 10 and 13 was feeded to construct crlf and to some it was so hard to type the whole chr()+chr() thing. so, it reasons somehow and @crlf was created. @tab would be a macro of single character and would reduce the length of invoking it from 6 to 4 characters. as a golf, that's a bad score. anyways, I think not all want to know their ascii tables and thus I would not rip off my pants if this came to happen. would just wonder a bit. |
||||||||
|
|
|||||||
Here's a quick little UDF for you... Code:
|
||||||||
|
|
|||||||
Haha, I know my ASCII chart very well, I dare say better then most here, probably comes from way to much assembly coding in the late 80's but since then I got lazy . But if @crlf is in I don't see the problem with building in this super mini thingy of @tab. On the other hand, quite a few macros can be "killed" since they are present as an environment variable or can be UDF'd in 1 or 2 lines of code. But, the 'vote' counts I guess... |
||||||||
|
|
|||||||
For what its worth, you have my vote iffy. |
||||||||
|
|
|||||||
You got my vote also. |
||||||||
|
|
|||||||
is it 3 to 2 now? |
||||||||
|
|
|||||||
Looks like it. I've always learned that majority rules |
||||||||
|
|
|||||||
hmm... I haven't. strenght of individual is what I count on |
||||||||
|
|
|||||||
having a feature just because we can, is not a good use of resources. I really see no need for this, since a chr(9) is just as easy to use. |
||||||||
|
|
|||||||
Perhaps I missing something, but I have never needed to use chr(9). I simply put a tab character in the string by pressing the tab button on my keyboard. This takes it down to 1 character; which is a hole-in-one in golfing terms. |
||||||||
|
|
|||||||
Quote: roflmao ... good one ! Beat that Lonk. |
||||||||
|
|
|||||||
I might need some time to come up with a witty reply on that one. |
||||||||
|
|
|||||||
hmm... no need I think. I actually am listening a song by DJ quicksilver. I herd wrong the first words of the song: "Shave up your a**" when she repeated them some seconds later, it really was "escape to an paraside" anyway, I use tab character in my codes too. but, inserting a tab is not just 1 character: Code:
as you can see, it actually is 4 characters. I actually think this is where the macro would come handy. instead of adding the tab to the string, with the macro it would be "easy" to embed it: Code:
|
||||||||
|
|
|||||||
No no with all due respect that is just plain wrong You've just chosen to write it a long way $stringwithoutTAB="text" $stringwithTAB="text " len($stringwithTAB)-len($stringwithTAB) = 1 |
||||||||
|
|
|||||||
k, my variable names were misleading, fixing: Code:
if you can do here a nice presentation of how tab affects the data, you can't in real life situation. in real life if you don't input the data yourself manually, it is given from somewhere and my example would be the way to add the tab to the text. |
||||||||
|
|
|||||||
And of course we all use SETOPTION('NoMacrosInStrings','ON'), thus @TAB requires at least six charatcers including the concatenation, no real advantage. |
||||||||
|
|
|||||||
ja, thanks jens. your wisdom is always welcome |