Re: [fpc-pascal] Google Drive API

2017-10-14 Thread Marcos Douglas B. Santos
On Sat, Oct 14, 2017 at 1:01 AM, leledumbo via fpc-pascal wrote: > Marcos Douglas B. Santos wrote >> I didn't found... In this path \packages\googleapi\examples only >> exists \generator directory. :( >> >> Trunk, rev 37453. > > Try this, it wasn't running well due to RTTI changes back then, but

Re: [fpc-pascal] CRT unit and Windows' terminal

2017-10-14 Thread Stefan V. Pantazi
I had a similar problem when trying to represent trees using extended ASCII characters. My solution was to adapt my character representations to UTF8. To see what I mean you can have a look at https://github.com/svpantazi/catalan-monoid-generator. The generate_catalan_monoid.pp contains a PrintASCI

Re: [fpc-pascal] JavaScript versions of pascal RTL functions (FormatFloat, DateToStr etc)

2017-10-14 Thread Mr Bee via fpc-pascal
Wow… that's really a great news, Michael! Thank you. I can't wait for it to be released officially. :) 2017-10-14 5:22 GMT+07:00 Michael Van Canneyt : > > > On Fri, 13 Oct 2017, Luiz Americo Pereira Camara wrote: > > Hi, >> >> I'm developing an app were the client is written in Javascript + HTML

Re: [fpc-pascal] CRT unit and Windows' terminal

2017-10-14 Thread wkitty42
for what ever reason, your code arrived here looking to be in UTF8 or ISO-8859-1 format... lazarus loaded is as ASCII but the box characters in the code were obviously not the ASCII ones you are speaking of (eg: ALT-201)... i tried to convert it to UTF8 in lazarus but the look was still the s

Re: [fpc-pascal] CRT unit and Windows' terminal

2017-10-14 Thread Tony Whyman
It may be worth looking at the SetTextCodePage in the System unit. On Windows targets I often find it necessary to include SetTextCodePage(output,cp_utf8); to avoid problems writing UTF-8 to the console. On 14/10/17 08:12, pasc...@piments.com wrote: On 13/10/17 14:39, James Richters wrote: I

Re: [fpc-pascal] CRT unit and Windows' terminal

2017-10-14 Thread Mr Bee via fpc-pascal
2017-10-14 14:12 GMT+07:00 : > > Thanks for that lengthy description of the problem, much better than OP's > just describing output as rubbish, or something similar. > since char is a single byte type a large value will just get truncated. If > you turn on range checking it should return a compi

Re: [fpc-pascal] CRT unit and Windows' terminal

2017-10-14 Thread pascalX
On 13/10/17 14:39, James Richters wrote: I‘ve tried Writeln(Chr(9556)) but chr() has a limit of 255, and I’ve tried just Writeln(#9556) and while that compiles and runs, it doesn’t produce the correct character.. I have a feeling (but have not tested it) that it keeps cycling around the first 2