Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | Microsoft released the compiler that ships with .NET 2003 Professional
>> | for free, here: http://msdn.microsoft.com/visualc/vctoolkit2003/
>>>
>> | Do we need to support anything older?
>> | Having said that, I see only two compiler work-arounds in Asger's
>> | patch, so let's say Asger's compiler ;-)
>>
>> I am asking because I need to know where to look in MS's
>> documentation.
>
| Hey, hey! What have we sucked you into?
I'll try to stay far, far away from it.
>> Anyway, I am tackling FileInfo first... the Q is: do we really need
>> it.
>>
>> The most advanced features of FileInfo is used by FileDialog.C in
>> xforms, but that is just a monster and I see that basically all other
>> file dialogs (gtk/qt/etc) are much simpler. So why not make it
>> simpler.
>
| Agree 100%.
>
>> F.ex. do we need to show the user that we have discovered a file to be
>> a socket or a fifo or a character type (or block)
>> IMHO we only need to differenciate between file and directory (and
>> _perhaps_ symbolic link.)
>
| Do it!
>
>> Also a lot of the other places we use FileInfo is just for one-shot
>> checking, checking stuff that we can get with boost.filesystem. So why
>> not use that instead?
>
| I would warn against exposing Boost.Filesystem to the rest of LyX for now.
| Guaranteeing that its obnoxious "this is not a portable file name" asserts
| are not triggered will require time and patience. However, if you're
| proposing to use it behind the scenes for 1.4.x, then I'm all for it.
in main we can call
fs::path::default_check(fs::no_check);
Then we don't care...
The Q is if we should do any of this for 1.4.x.
--
Lgb
