Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • sac2c sac2c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 395
    • Issues 395
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • sac-group
  • sac2csac2c
  • Issues
  • #1098
Closed
Open
Created Oct 07, 2011 by Clemens Grelck@cgDeveloper

Specialize directive requires parameter names

Bugzilla Link 878
Created on Oct 07, 2011 19:41
Version svn
OS All
Architecture PC

Extended Description

Currently, the specialization directives need both a return type and parameter names in addition to types. In particular, the latter is counter-intuitive for C programmers. This should be easy to fix in the parser. 
The return type(s) could be made optional as they are not relevant in the specialisation. Likewise, the names of parameters.
We should also consider to make the specialisation directive a proper pragma:
#pragma specialize blaBlub( int[10,10], float)
instead of the current syntax. Both SAC and C provide pragmas for exactly this kind of purpose.
All these proposals are not particularly urgent, but would be a few mosaic stones in making SAC more customer-friendly and, with respect to the pragma, a bit more consistent.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking