The {$M} directive can be used to set the stack and heap size.

How can I find out what the default stack and heap sizes are if {$M} is NOT used?

Mark

Mark Emerson wrote

The {$M} directive can be used to set the stack and heap size. How can I find out what the default stack and heap sizes are if {$M} is NOT used?

I'm not sure if they're documented anywhere, but they don't really matter: they all grow automatically as your program needs more of them under all supported OS'es currently.

Jonas

This is extremely good news. Let me ask (to be certain I understand), can the stack effectively grow the the limit of memory? Or will there be an artificial ceiling?

Mark

Hi,
Part of my icafe system (which is written entirely in FPC) is the countdown timer which is displayed to users. This uses SDL for the back end.
Does anybody know how to tell SDL to make a window act in an always on top manner ?
This has been specifically requested by the customers of several of the Icafe's where the project is being piloted.

Remotely related: Does anybody know why SDL apps would crash X on:i cyberblade cards when it is run in fullscreen mode ? I discovered this while working on the SDL version of the Graph unit. It happens regardless of video mode btw. The same card also tends to get messy with XV programs, looking like a TV with a signal interference if you run ogle. The crash is utter and complete - so much so that the only way to get out of it short of a hard-reset is to ssh in and reboot over the net.

Ciao
A.J.

Mark Emerson wrote

This is extremely good news. Let me ask (to be certain I understand), can the stack effectively grow the the limit of memory? Or will there be an artificial ceiling?

I don't think there are any real limits, except when you have multithreaded programs (then the stack is limited to +-1MB per thread under Linux and to the value you specify using {$m ...} or with the -Cs command line parameter under Windows due to OS/library limitations)

Jonas