Re: [fpc-devel] FPC compiles malformed code

2006-08-24 Thread Michael Müller
Am 24.08.2006 um 04:04 schrieb Graeme Geldenhuys: Maybe because pascal is insensitive to whitespace between tokens. You also can write: lData.Name:='Graeme'; and lData.Name := 'Graeme'; I understood that as: between the symbols etc... eg; := or = or , Never thought that would mean betw

Re: [fpc-devel] FPC compiles malformed code

2006-08-24 Thread Graeme Geldenhuys
Maybe because pascal is insensitive to whitespace between tokens. You also can write: lData.Name:='Graeme'; and lData.Name := 'Graeme'; I understood that as: between the symbols etc... eg; := or = or , Never thought that would mean between a Class and a property/function. Interesting but

Re: [fpc-devel] FPC compiles malformed code

2006-08-24 Thread Vincent Snijders
Graeme Geldenhuys wrote: Hi, Shouldn't FPC complain about the code below - I marked the lines with comments. lData.Name is typed as lData .Name the same for the function lDate.AsString is typed as lData .AsString. Notice the space before the dot... - CUT

[fpc-devel] FPC compiles malformed code

2006-08-24 Thread Graeme Geldenhuys
Hi, Shouldn't FPC complain about the code below - I marked the lines with comments. lData.Name is typed as lData .Name the same for the function lDate.AsString is typed as lData .AsString. Notice the space before the dot... - CUT - program project1; {$m