From: marcov@stack.nl   
      
   On 2005-02-03, RadSurfer  wrote:   
   > const   
   > manifest = 1234;   
   >   
   > Why does const use   =    and not   :=   ?   
      
   = is an equality. Left is always the same as right.   
   := is an assignment. For now we put the right in value in X, but that doesn't   
   mean it is always like that.   
      
   However Borland got a bit inconsequental with   
      
   const a : integer =5;   
      
   and   
   var a : integer =5; {Delphi4+}   
      
   > procedure A_Procedure(A,B:integer; C,D:longint);   
   >   
   > commas where alile, and semi's between different types...ok.   
   >   
   > type   
   > A_Type = Record;   
   > ...   
   > end;   
   >   
   > again, use of   =    instead of   :=   
      
   atype is always that record. It doesnt change, so an equality.   
      
   > One conclusion that comes to mind,  = (equals) is used when the   
   > declaration can not be changed;   
   > whereas  :=  is with dynamic variables which would change frequently   
      
   Correct.   
      
   > Another thing:   
   > for / to / do [begin/end],   
   > repeat/while   
   > do/until, etc   
   >   
   > What about what 'C/Cpp' would call 'continue' and 'break' ?   
      
   TP7 has them iirc. They are called continue and break too.   
   Try if it works, if not, it was a later addition.   
      
   > I really think 'C/Cpp' was vastly much easier on the intuitive-scale then   
   > Pascal is. 'C/Cpp' offers so many powerful features and usually powerful   
   > libraries that I doubt I would permanently switch to TPascal; but I am   
   > going to stay with this and see what surprises surface.   
      
   That's because you try to use a pre 1990 compiler here. For something modern,   
   try Free Pascal.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)