To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 8468
8467  |  8469
Subject: 
Re: Backwards Compatibility (Was Calling all Meta-commands)
Newsgroups: 
lugnet.cad.dev
Date: 
Sun, 16 Mar 2003 19:16:07 GMT
Viewed: 
2214 times
  
In lugnet.cad.dev, Dan Boger writes:
I'm sorry, I can't understand why it's "too difficult" to enter {} by
hand.  It's on the standard keyboard.  The people who actually edit
stuff by hand have the requirement of knowing how to use a keyboard :)
I mean, when SMTP format was design, you think they were worried that
people will have a hard time typing "@"? *grin*

By adding the {}, we ensure that a mistake like this just couldn't
happen.  Or at least very unlikely to happen.

Just my $0.02

:)

I don't know about American keyboards, but at my Swedish kb, '{' and '}' are
at AltGr+7 and AltGr+0, and it collides with Swedish special characters in
the ASCII table; it has to be set on codepage 850 or whatever it was. I find
them somewhat hard to find even though I program in C from time to time.
And, for example, when printing out C code from a Swedish OS, it happens
very often that those brackets come out totally wrong. Well, such problems
are less common than for some years ago, but still it is a source for
errors. (Look at some posts at lugnet.loc.se, and you'll see what those
ASCII table settings can course!)

My SEK 0.50 is that we *recommend* the use of a comment sign. We can discuss
if it should be // ' COMMENT ; /*...*/ or the one I've used some times: REM.
COMMENT is the one I've seen in use most times, but it's lo-o-ong IMHO.
Maybe more than one, (maybe maybe all of them)

META or maybe {META} would be neat, but only for future meta-commands. I
would prefer a shorter sign there, too: Like $ without space. $LTRAX for
example.

One more thing: The header has severeal lines of file info. This info could
be even more standardized, but I don't like to see any META or COMMENT signs
there, that will only make it harder for people to read, and call to a
massive software update with little gain.

So, to make this spec work even more complicated I suggest there will be a
difference between compulsary usage and recommended ditto.


/Tore



Message has 1 Reply:
  Re: Backwards Compatibility (Was Calling all Meta-commands)
 
(...) What I mean is: (URL) for example. Quite corrupted and hard to read - even for us who understand Swedish. ;-) I don't know whether brackets will be cause the same kind of problems, but there is a risk. Then a line from a posted part or model (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)

Message is in Reply To:
  Re: Backwards Compatibility (Was Calling all Meta-commands)
 
(...) Exactly because it's not likely to be used, ever, by mistake. Anyone can put whatever comments they like in a dat, right? So if I write a dat, and want to enter 0 METAL RAIL STARTS HERE and typo it into 0 META LRAIL STARTS HERE (which is a (...) (22 years ago, 16-Mar-03, to lugnet.cad.dev)

154 Messages in This Thread:
(Inline display suppressed due to large size. Click Dots below to view.)
Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR