[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

342.0. "Using == (double equal signs)" by AUTHOR::R_MCGOWAN () Tue May 05 1987 14:26

We need to use double equal signs, and we've discovered that:

   (1)  <code_example>
         y == 2x
        <endcode_example>
    
   produces  y == 2x

   (2)  <code_example>(==) 

   produces   = =  (with an added space between the equal signs)

   (3)  <math>(==)

   produces   ==   (just what we wanted with no added space)

However, shouldn't <code_example>(==) produce == with no added space.
Is this a bug?
T.RTitleUserPersonal
Name
DateLines
342.1it was worse beforeCLOSET::ANKLAMTue May 05 1987 18:146
    
    Yes, there is some internal translation done on the occurrence of
    two equal signs together in a text (i.e. not monospaced and not
    math) format. You mean you want the equals signs run together?
    
    
342.2AUTHOR::WELLCOMESteveWed May 06 1987 10:3810
    No, not run together. We want them to look like two consecutive
    equal signs with no intervening space character.  Right now it 
    looks like <equal sign> <space character> <equal sign>. We want 
    it to look like this, ==, just what you're seeing on your screen, 
    not like = =, which is very misleading and suggests that there 
    is an intervening space character.  Since this is a code example, 
    there can't be ambiguity in what the exact characters are.  This
    happens to be for MACRO-11, but the same thing would apply to a
    description of VMS DCL and the :== construction; it's :==, not := =.
    
342.3Double HyphensSTAR::GILLIAMWed May 06 1987 16:2919
We've noticed a similar situation trying to produce two hyphens in a row.
Two hyphens makes an n-dash. Three hyphens generates an em-dash and
so on. The writer needs to specify null fields within an absolute time
specification.

Here's a test file.

<table>
<table_setup>(2\10)
<table_heads>(A\B)
<TABLE_ROW>(<LITERAL>(--)\A)
<TABLE_ROW>(<LITERAL>(-)<LITERAL>(-)\B)
<TABLE_ROW>(- -\C)
<TABLE_ROW>(--\D)
<TABLE_ROW>(----\E)
<TABLE_ROW>(<LITERAL>(--)<LITERAL>(--)\F)
<ENDTABLE>

Mason