Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-22 Thread Marco van de Voort
On Monday 21 January 2008 18:45, Marco van de Voort wrote: I have missed opague types and forcedly qualified importing (from M2) Well, I miss them too. As I'll show you in a moment that they even go hand in hand with child packages. M2 doesn't have the nested module put in

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-22 Thread Vinzent Hoefler
On Tuesday 22 January 2008 09:48, Marco van de Voort wrote: Maybe. Keep in mind that opague is roughly comparable with type tmyopaguetype = type pointer; Since the interface must 100% define the interface so that it can be used, which is a hard rule with Pascal and Modula2. Hmm, what if

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-22 Thread John Stoneham
On Jan 22, 2008 2:48 AM, Marco van de Voort [EMAIL PROTECTED] wrote: [snip] ... an import of complexnumbers in one place might suddenly react differently due to the partial module/classhelper) Then you misunderstand the concept. While it's true that child packages are similar to nested

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-22 Thread Marco van de Voort
type tmyopaguetype = type pointer; Since the interface must 100% define the interface so that it can be used, which is a hard rule with Pascal and Modula2. Hmm, what if --- 8 --- interface type tMyOpaqueType; // Incomplete. private type // Complete type

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-22 Thread Tony Pelton
On Jan 21, 2008 12:05 PM, John Stoneham [EMAIL PROTECTED] wrote: On Jan 21, 2008 1:05 AM, Vinzent Hoefler [EMAIL PROTECTED] wrote: On Friday 18 January 2008 20:12, John Stoneham wrote: Perhaps that's true with regard to name resolution, but Ada's package system has a significant feature

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-22 Thread Vinzent Hoefler
On Tuesday 22 January 2008 21:36, Marco van de Voort wrote: type tmyopaguetype = type pointer; Since the interface must 100% define the interface so that it can be used, which is a hard rule with Pascal and Modula2. Hmm, what if --- 8 --- interface type

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-21 Thread Marco van de Voort
I think it would be fantastic if Free Pascal could add child units as a language extension (of course this would reduce portability -- although on the other hand it might make porting Ada programs easier). It's difficult trying to describe the benefits to someone who has never used them

Re: [fpc-pascal] child units (was: dot within unit file name)

2008-01-21 Thread Vinzent Hoefler
On Monday 21 January 2008 18:45, Marco van de Voort wrote: I think it would be fantastic if Free Pascal could add child units as a language extension (of course this would reduce portability -- although on the other hand it might make porting Ada programs easier). It's difficult trying to