Michael Schnell wrote:
On 07/13/2010 06:27 PM, Jonas Maebe wrote:
b) indeed also because of the searching for filenames with different
cases.
It might sometimes indeed make sens to not be forced to use the same
name for the unit and the file containing it's source code.
So using "in" with just a file name, without the obviously
non-portable directory notation, and thus (hopefully) having the
compiler search in the normal unit search path does make sense.
-Michael
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.830 / Virus Database: 271.1.1/3003 - Release Date: 07/13/10 20:36:00
Yes, but that defeats unit aliasing by renaming: like "uses foo in
"bar.pas"" instead of "uses foo" (implies "in foo.pas"). Did somebody
mention this in the discussion?
Programmers are not very imaginative in naming. It is plainly helpfull
to be able to rename a file if another file with a different content.....
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
