Re: [fpc-pascal] StrToInt is using ShortString buffer?

That is another reason for PChar based inner func. :) the input might be

[fpc-pascal] StrToInt is using ShortString buffer?

Hello. As I see in the commit https://gitlab.com/freepascal.org/fpc/source/-/commit/beecbf1581a986f544fde77aa428e05c21a35f6f StrToInt always uses ShortString buffer: *Function fpc_Val_SInt_ShortStr(DestSize: SizeInt; Const S: ShortString; out Code: ValSInt): ValSInt;* If it is correct: Can

[fpc-pascal] FP wiki shows bad picture sizes

Picture at https://wiki.freepascal.org/CudaText#Lexers and at https://wiki.freepascal.org/CudaText#Lexers_editing both shown with wrong sizes -- left from old picture  versions. Upload of new pics gave "red error text". -- Regards, Alexey ___

[fpc-pascal] FPC 3.2.1 gdeque Erase(0) hangs forever

CudaText for linux x64. gdeque (fcl-stl) method Erase(0) (list has single item) hangs. I made workaround- replaced Erase(i) with Clear (erase all items). deque items - not managed.   PATAdapterCacheItem = ^TATAdapterCacheItem;   TATAdapterCacheItem = packed record     LineIndex, CharIndex,

[fpc-pascal] TProcess doc page bugs

>No, read-only. It's input from the point of view of the *parent process*. Doc is blurry. Can you write there - what streams (3: input/ output/ stderr) are OK for ReadInputStream ? -- Regards, Alexey

[fpc-pascal] TProcess doc page bugs

>It's an input pipe stream, which is by definition read-only. Input is read-only?? it's write-only I guess. >It automatically follows you can only read from Output and StdErr streams. Then we need ". from Output/StdErr streams" text there. Cur text is misleading. Alexey

[fpc-pascal] TProcess doc page bugs

https://www.freepascal.org/docs-html/current/fcl/process/tprocess.readinputstream.html a) it has 2 sections "Arguments" (mixed with "Func result")- pls make nicer output: "Arguments (variant 1)", "Arguments (variant 2)", "Function result" b) first variant of func has "public" mark - it's

[fpc-pascal] TProcessUTF8 doc - 2

a) https://lazarus-ccr.sourceforge.io/docs/lazutils/utf8process/tprocessutf8.html here we have 2-3 items depre - ApplicationName, CommandLine. but list shows no special mark. confusing. it shows [rw] marks, pls add near the [deprecated] marks. b)

[fpc-pascal] TProcessUTF8 doc - 2

a) https://lazarus-ccr.sourceforge.io/docs/lazutils/utf8process/tprocessutf8.html here we have 2-3 items depre - ApplicationName, CommandLine. but list shows no special mark. confusing. it shows [rw] marks, pls add near the [deprecated] marks. b)

[fpc-pascal] TProcessUTF8 doc - 2

a) https://lazarus-ccr.sourceforge.io/docs/lazutils/utf8process/tprocessutf8.html here we have 2-3 items depre - ApplicationName, CommandLine. but list shows no special mark. confusing. it shows [rw] marks, pls add near the [deprecated] marks. b)

[fpc-pascal] TProcess.CurrentDirectory doc

https://lazarus-ccr.sourceforge.io/docs/fcl/process/tprocess.currentdirectory.html CurrentDirectory specifies the working directory of the newly started process.Changing this property after the process was started has no effect. need more info there! a) what happens when the process, eg Bash

[fpc-pascal] optimization for strlicomp()

function strlicomp(str1,str2 : pwidechar;l : SizeInt) : SizeInt;   var    counter: sizeint;    c1, c2: char;   begin     counter := 0;     if l=0 then   begin     strlicomp := 0;     exit;   end;     repeat   c1:=simplewideupcase(str1[counter]);  

[fpc-pascal] Array of const: docs

https://www.freepascal.org/docs-html/ref/refsu69.html Remark: Note that there is no support for QWord arguments in array of const. This is for Delphi compatibility, and the compiler will ignore any resulting range checks when in mode Delphi. but the code shows that QWord is supported. huh?