Search found 204 matches
- Sat Dec 14, 2019 10:13 pm
- Forum: Resolved (Features)
- Topic: issue-#156 adding Coroutines to BlackBox
- Replies: 108
- Views: 209195
Re: issue-#156 adding Coroutines to BlackBox
I don't see any inconsistency. The Kernel is not required or defined by the Language Report. Coroutines are not required or defined by the Language Report. e.g. Gardens Point Component Pascal complies with the report. If a coroutine-like functionaility is required for a GPCP application then that is...
- Tue Dec 03, 2019 7:46 pm
- Forum: Resolved (Bugs)
- Topic: issue-#197 Problems with Coroutines
- Replies: 12
- Views: 15068
Re: issue-#197 Problems with Coroutines
Was that pun intentional?Robert wrote:... which involved multiple compile unload cycles.
![Wink ;)](./images/smilies/icon_e_wink.gif)
- Mon Feb 11, 2019 1:14 am
- Forum: Discussion
- Topic: Consistent import
- Replies: 9
- Views: 17723
Re: Consistent import
You can use Info > Dependency to draw a dependency graph and Info > Create Tool to generate a set of commands to recompile everything in the correct order. However, as far as I can see, these commands require object files :( . As your top-level module fails to compile you might need to create a tool...
Re: KeyWord
Since the practical implications are zero, I cannot understand why a fix of this inconsistency in the report should not be possible. The problem is that you would then break the Gardens Point Component Pascal compiler which implements the language as defined in the report. In that case the intentio...
Re: KeyWord
We are left with the (minor) problem that the reserved words ABSTRACT, EMPTY, EXTENSIBLE, & LIMITED can be redefined without compile time error, but this is forbidden by the Language Report. My recommendation would be to just put a note mentioning it as a limitation of the BlackBox implementati...
Re: KeyWord
Isn't the genie the fact that predeclared identifiers can be redefined at all? The reason behind not defining predeclared identifiers as reserved words is not so that you can redefine them. The reason is to protect you from future language changes: When new predeclared identifiers are introduced (e...
Re: KeyWord
How can a name (NEW) be a standard procedure AND a reserved word at the same time? It can be either the one or the other, but not both. Or can it? NEW isn't both 'at the same time' - it can be context sensitive. Consider this example: MODULE CfbNew; TYPE T = RECORD i: INTEGER END; VAR ptr: POINTER ...
Re: KeyWord
The distinction between keywords and predefined objects is a subtle topic. Why does it exist at all? I mean, why aren't for example the basic types (INTEGER, etc.) not keywords but predefined types? In my understanding the reason for inventing and using the concept of predefined objects is upgrade-...
Re: KeyWord
I checked the text example in the other major implementation of Component Pascal (GPCP) and it failed to compile as I would have expected. The CP language report defines EXTENSIBLE, ABSTRACT and LIMITED as reserved words and explicitly states that they 'cannot be used as identifiers'. However I agre...
- Mon Nov 19, 2018 8:23 pm
- Forum: Resolved (Documentation)
- Topic: issue-#190 add comment about stack and heap memory config.
- Replies: 9
- Views: 13922
Re: issue-#190 add comment about stack and heap memory confi
Just two minor typos:
(extra space before icons and missig is missing the 'n')
Code: Select all
squares instead of icons, missig tree view,