51

Re: Winbuntu

Hello, IID, you wrote: S>> So why MinGW-w64 for this task is a crutch? IID> for development, and under Windows? Mighty well you change a subject. Under Windows it does not suit development at all. And ++ under Windows you can offer what made compiler of a C, except gcc? - A poor hand-made article from MS to offer simply ridiculously (the Author see for example here https://rsdn.org/forum/cpp/6722631.1: alex_public Date: 11.03.17, and for a year exchanged nothing https://rsdn.org/forum/cpp/7014553.1 the Author: Nuzhny Date: 09.01 15:45). - clang it is certainly good the error messages and standard support, but on optimization concedes to all remaining. - the compiler from Intel? There with high-speed performance all is just good, but the standard is supported not so operatively and plus unlike all remaining it costs decent money. So whom else you will offer, if not MinGW?)

52

Re: Winbuntu

Hello, Artem Korneev, you wrote:> Installing a packet xorg-dev you can write and launch X-Windows applications under WSL. AK> Wine works?

53

Re: Winbuntu

IID> And anybody  also did not promise of 100 % IID> Come on WSL page . Therefrom there are links to lists of a software which works badly. The title ' Windows Subsystem for Linux ' likely was invented by that person as WoW64.

54

Re: Winbuntu

Hello, ononim, you wrote: O> the Title ' Windows Subsystem for Linux ' likely was invented by that person as WoW64. In Soviet Russia...

55

Re: Winbuntu

MS>> From the point of view of NTFS the unique forbidden character in a name is 0 IID> From the point of view of a flow name on file system and a data storage format, but not from the point of view of OS. IID> see FsRtlIsAnsiCharacterLegalXXXX which checks a flag of availability ASCII of characters in built in  (Fat/Hpfs/Ntfs). IID> On NTFS are forbidden: IID> 0x00-0x1F IID> 0x22 (") IID> 0x2A (*) IID> 0x2F (/) IID> 0x3C (<) IID> 0x3E (>) IID> 0x3F (?) IID> 0x5C (\) IID> Except restrictions  it is necessary to be punched through the manager of objects, at it on reverse slashes the sight. There are also restrictions on names CON/PRN/COM1 and other. Really it too file system restrictions? In all implementations known to me ntfs.sys restriction on an amount of clusters - 32 bits though the file system supports 64 bit addressing the Prohibition of creation hardlink on directories - implementation restriction. All these examples speak only about implementation restrictions. I spoke about restrictions . In other implementations of the specified restrictions is not present. MS>> In  it also is forbidden IID> And what with  in ? On a poppy screens. On  I do not know.

56

Re: Winbuntu

Hello, , you wrote: MS>> From the point of view of NTFS the unique forbidden character in a name is 0 MS>> In  it also is forbidden > In NTFS like UTF-16. How 0 can be there forbidden? In ondisk structures the length of a name and if in this name is 0 chkdsk deletes such name is registered.

57

Re: Winbuntu

Hello, AlexGin, you wrote: AG> "my" system MS Windows, on it I am engaged with 90 and I continue to this day. AG> and about MSVC-2017 on c ++ 17, c than I work daily, at me here questions were not. AG> itself to a clod you want I will tell. In MSVC Cs ++ VLA already added?