You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While in development phase, the user should be able to update an existing release.
In the best case, smap should be able to know which releases were released and which were not. Maybe it could be done with an special comment syntax for released releases. As in:
#@ released
LIBX_1_2_3
{
global:
symbol;
local:
*;
} ;
or simpler:
LIBX_1_2_3 # released
{
global:
symbol;
local:
*;
} ;
The text was updated successfully, but these errors were encountered:
- Added "--final" option to mark the changed release as final
- Allow user to update an existing release
- Do not allow user to modify a released release
- Use dictionaries for visibility scopes
- Merge visibility scopes with the same name when parsing
Fixes#65, #62, #60
While in development phase, the user should be able to update an existing release.
In the best case, smap should be able to know which releases were released and which were not. Maybe it could be done with an special comment syntax for released releases. As in:
or simpler:
The text was updated successfully, but these errors were encountered: