On Thu, Dec 27, 2018 at 7:02 PM Bart wrote:
>
> On Thu, Dec 27, 2018 at 4:48 AM Dennis wrote:
>
> > > Rest in peace Martin Schreiber.
>
> That's very sad news indeed.
>
Oh no
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.free
ate between a language feature
and its common implementation. Perhaps case statements with variables
make sense? Of course, that doesn't mean anyone is going to add them.
I suggest the OP look up pattern matching. Scala may be more readable
than Haskell, and there is also OCaml.
Cheers,
R0b0t1
_
the opengl rendering. Is that possible? How?
>
This seems to be the obvious usecase. Can some clarification be
provided? E.g. SDL2 needs to manage the OpenGL contexts, does this
library manage them as well?
Cheers,
R0b0t1
___
fpc-pascal maillis
Noice.
I'd been wanting to collect all of the ones from the docs into a more
coherent representation of the syntax.
On Tue, Sep 11, 2018 at 1:49 PM, Anthony Walter wrote:
> I posted this link once before, but I thought I'd remind you guys it
> exists and ask if anyone would like to take the wor
On Fri, Aug 24, 2018 at 2:45 PM, Mark Morgan Lloyd
wrote:
> On 24/08/18 09:15, R0b0t1 wrote:
>>
>> On Thu, Aug 23, 2018 at 6:28 AM, Mark Morgan
>> Lloyd wrote:> On 23/08/18 10:00, Martin
>> Schreiber wrote:>>>> On Thursday 23 August 2018 11:11:34 Bo Bergl
ot;realtime" kernel.
I do think this could be done by beating the SPI peripheral over the
head, but just like the solution involving timers it may not be easy
to implement as you need to slide your code in to Linux.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
uler. Or perhaps not.
I usually like to stick a small ARM chip somewhere (used to be an AVR)
to handle these things as the hardware is usually more configurable.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lis
details of the device nodes.
Creating headers for and calling that code may or may not save you any
work. Some of those libraries, like the devicemode USB one,
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.f
hasn't already claimed it (like for power
management bus).
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
consistent group of proposals. It will prevent needing
to create a lot of special keywords:
var
c: thread TMyClass;
d: auto TMyClass;
Or, perhaps even better:
thread var
c: TMyClass;
managed var
d: TMyClass;
Cheers,
R0b0t1
On Thu, Jul 26, 2018 at 10:19 PM, Ryan Joseph
wrote
On Mon, Jul 23, 2018 at 11:11 AM, Ryan Joseph
wrote:
>
>
>> On Jul 22, 2018, at 4:54 AM, Sven Barth via fpc-pascal
>> wrote:
>>
>> And that's why there are people who *do* care about it. Of course you can
>> put everything and the kitchen think into a language. But if it doesn't fit
>> the lan
out software.
It's not to say all of these things are bad - it's just I wish more
thought would have gone into them. Perhaps that would mean changing
the feature so much that it doesn't resemble what was originally
proposed.
Cheers,
R0b0t1
_
On Wed, Jul 18, 2018 at 4:08 PM, Sven Barth via fpc-pascal
wrote:
> R0b0t1 schrieb am Mi., 18. Juli 2018, 21:46:
>>
>> On Wed, Jul 18, 2018 at 2:04 PM, Ryan Joseph
>> wrote:
>> >
>> >
>> >> On Jul 18, 2018, at 12:44 PM, Sven Barth via fpc
On Wed, Jul 18, 2018 at 3:57 PM, Sven Barth via fpc-pascal
wrote:
> Ryan Joseph schrieb am Mi., 18. Juli 2018,
> 21:37:
>>
>>
>>
>> > On Jul 18, 2018, at 12:44 PM, Sven Barth via fpc-pascal
>> > wrote:
>> >
>> > And to give you a slightly different example: around a year ago or so I
>> > impleme
ems with
typing are indicative that the language could use a more expressive
type system, not that it was a good idea to create an intrinsic that
could (potentially) ignore types.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
On Mon, Jul 16, 2018 at 3:28 PM, Sven Barth via fpc-pascal
wrote:
> Am 16.07.2018 um 19:55 schrieb R0b0t1:
>>
>>
>>> - Try except finally blocks
>>
>> I can support this one, I am surprised it is not already supported.
>> Wasn't this mentione
; things in either a private class method or
in method variables.
FPC is already lacking in some major ways compared to Delphi. The main
one I can think of is anonymous functions. If anyone could implement
that the community would benefit immensely.
I've looked, on and off, but not been
ess relating to
isochronous transfers that is rather lengthy that I did not include
due to time.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
On Sun, Jul 1, 2018 at 5:51 PM, Ryan Joseph wrote:
> Is there a way to make a constant for a list of chars which I can use in a
> case statement? I’ve got a bunch of code duplication happening I’d like to
> clean up.
>
> const
> TChars = ('[', ']', '(', ')', '{', '}', '=', ‘:’);
>
>
> case c o
On Sun, Jul 1, 2018 at 8:06 AM, Marcos Douglas B. Santos
wrote:
> On Sat, Jun 30, 2018 at 9:13 PM, R0b0t1 wrote:
>> Anyway - does TTimer use the WM_TIMER message? That is the type tied
>> to the GUI. Even if you need to use WM_TIMER for some reason you can,
>> as serv
s/windows/desktop/sync/using-waitable-timer-objects).
Using waitable timers you can also wake the computer from sleep.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
faceDetail(
hDevInfo,
&DevIntData,
pDevIntDetData, RequiredSize,
NULL,
&DevInfoData
);
r.push_back(wstring(pDevIntDetData->DevicePath));
free(pDevIntDetData);
}
}
re
sted. When was it added?
>
> Regards,
> Ryan Joseph
>
I found them one day as well and was confused. The note that they implement
TMonitor is helpful. I know of no other uses.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.fr
n if it is not, getting your codebase compatible with Lazarus/FPC
is likely a good longer term goal.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
e.g. PlayStation custom OS. Precluding open-source
> support from both FPC and Castle Game Engine for the consoles. Any code that
> uses some API covered by NDA must be closed-source, can be available only to
> people who also signed the NDA.
>
If you contact MS they may get back to
e using curl:
>
> curl -u user:pwd -F "image=@firmware.bin" :80/firmware
>
I'd strongly recommend using SSH/SCP instead, or at least HTTPS.
Certificates for HTTPS can be more difficult to set up on nontechnical
user's computers.
Cheers,
R0b0t1
> I don
s to use a log function that
behaves differently based on the verbosity level.
Cheers,
R0b0t1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
On Thu, Apr 12, 2018 at 1:10 AM, Graeme Geldenhuys
wrote:
> On 2018-04-11 17:44, R0b0t1 wrote:
>> This is related to something I meant to propose a while ago related to
>> a cross platform timing and alarm API.
>
> That already exists in the form of EpikTimer
> (ht
On Wed, Apr 11, 2018 at 12:11 PM, Tomas Hajny wrote:
> On Wed, April 11, 2018 18:44, R0b0t1 wrote:
>
> .
> .
>> This is related to something I meant to propose a while
>> ago related to a cross platform timing and alarm API.
>> I do not think GetTickCount s
s platform timing and alarm API. I do not think GetTickCount
should ever be used; instead, QueryPerformanceCounter makes more
sense. It is higher resolution and still portable. The Linux function
`clock_gettime` called with `CLOCK_REALTIME_HR` is more or less a
direct equivalent.
Cheers,
R
On Mon, Mar 5, 2018 at 1:54 PM, Michael Ring wrote:
> @R0b0t1:
>
> FYI, I have now implemented Clock Configuration and gpio for stm32l4 chips,
> the blinky program works now, please pull latest mdf libs from github.
>
Thank you Michael, it may be some time before I can work with t
On Thu, Mar 1, 2018 at 3:11 PM, R0b0t1 wrote:
> On Thu, Mar 1, 2018 at 2:46 PM, Marc Santhoff wrote:
>> On Wed, 2018-02-28 at 06:41 +0200, Christo Crause wrote:
>>> On 28 Feb 2018 4:22 am, "R0b0t1" wrote:
>>>
>>> I will be following up wi
On Thu, Mar 1, 2018 at 2:46 PM, Marc Santhoff wrote:
> On Wed, 2018-02-28 at 06:41 +0200, Christo Crause wrote:
>> On 28 Feb 2018 4:22 am, "R0b0t1" wrote:
>>
>> I will be following up with you off list, since you do not seem to mind.
>>
>>
>
On Wed, Feb 28, 2018 at 11:27 AM, Michael Ring wrote:
> Am 28.02.18 um 03:22 schrieb R0b0t1:
>>
>> On Tue, Feb 27, 2018 at 2:43 AM, Michael Ring
>> wrote:
>>>
>>> The process is completely automated and is based on converting the header
>>> files t
be achieved in some other way than a HAL. This may be
due to how peripheral mappings are supplied. Perhaps there is a better
way I do not know about. Large projects such as
https://github.com/qmk/qmk_firmware manage.
I will be following up with you off list, since you do not seem to mind.
Che
king with FPC.
What complicates things is the way libopencm3 has their headers
structures is more standard. They avoid using structures that
represent the registers, instead using faux namespacing with lots of
underscores in macro names.
Cheers,
R0b0t1
___
36 matches
Mail list logo
