Hello,
I was porting to Linux some Windows code which uses critical
sections API, and got 'Identifier not found' error on InitializeCriticalSection
and
DeleteCriticalSection symbols. After searching through RTL code, I
discovered that abovementioned functions are named InitCriticalSection
and
On Wednesday 04 April 2007 10:33, Sergei Gorelkin wrote:
I was porting to Linux some Windows code which uses critical
sections API, and got 'Identifier not found' error on
InitializeCriticalSection and DeleteCriticalSection symbols.
If I had to guess, I'd say this is probably because those
Wednesday, April 04, 2007, 3:00:55 PM, Vinzent wrote:
After
searching through RTL code, I discovered that abovementioned
functions are named InitCriticalSection and DoneCriticalSection. At
the same time, the EnterCriticalSection and LeaveCriticalSection are
not renamed, so code using them
Sergei Gorelkin wrote:
But EnterCriticalSection/LeaveCriticalSection also exist in Windows API.
And they are implemented in System unit without changing names. Therefore, to
They shouldn't be exposed publicly in the system unit.
Micha
___
fpc-devel
On Wednesday 04 April 2007 12:59, Sergei Gorelkin wrote:
But EnterCriticalSection/LeaveCriticalSection also exist in Windows
API. And they are implemented in System unit without changing names.
Therefore, to make my code cross-platform, I have only to remove
Windows from uses clause - then
On Wednesday 04 April 2007 13:13, Micha Nelissen wrote:
Sergei Gorelkin wrote:
But EnterCriticalSection/LeaveCriticalSection also exist in Windows
API. And they are implemented in System unit without changing
names. Therefore, to
They shouldn't be exposed publicly in the system unit.
Wednesday, April 04, 2007, 5:13:43 PM, Vinzent wrote:
VH On Wednesday 04 April 2007 12:59, Sergei Gorelkin wrote:
But EnterCriticalSection/LeaveCriticalSection also exist in Windows
API. And they are implemented in System unit without changing names.
Therefore, to make my code cross-platform,
En/na Sergei Gorelkin ha escrit:
The code I was compiling was already cross-platform (Delphi/Kylix),
and 'uses Windows' was wrapped by {$IFDEF MSWINDOWS}. In Kylix,
InitializeCriticalSection and DeleteCriticalSection are implemented in
SysUtils unit, so any code using these functions continue
Go to translatable web site
leads to error dump:
can't read locale_admin_url: no such variable
while executing
lang::util::localize ${locale_admin_url}
invoked from within
if {[string equal [ad_quotehtml [lang::util::localize
${translatable_website}]] 1]} {
append __adp_output
1. I18N Message Conflicts shows pl_PL locale conflicts. Is it right or is it
wrong? (I want to check ru conflicts if any.)
2. Would it be better if this or similar questions were posted as bugs?
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
10 matches
Mail list logo
