Bug 387014 - no function warnings for gsl\parser.h
Summary: no function warnings for gsl\parser.h
Status: RESOLVED FIXED
Alias: None
Product: LabPlot2
Classification: Applications
Component: backend (show other bugs)
Version: latest
Platform: Microsoft Windows Microsoft Windows
: NOR minor
Target Milestone: ---
Assignee: Stefan Gerlach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-16 23:19 UTC by uwestoehr
Modified: 2017-11-23 23:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description uwestoehr 2017-11-16 23:19:28 UTC
I get:

2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(42): warning C4255: 'fnct': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(49): warning C4820: 'parser_var': '6' bytes padding added after data member 'name'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(53): warning C4255: 'func_t': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(62): warning C4820: 'symrec': '4' bytes padding added after data member 'type'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(66): warning C4255: 'init_table': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(67): warning C4255: 'delete_table': no function prototype given: converting '()' to '(void)'
2>C:\CraftRoot\labplot\src\backend\gsl\parser.h(68): warning C4255: 'parse_errors': no function prototype given: converting '()' to '(void)'
Comment 1 Stefan Gerlach 2017-11-22 09:46:57 UTC
please check again.
Comment 2 uwestoehr 2017-11-22 23:18:55 UTC
> please check again.

Now I get:

3>C:\CraftRoot\labplot\src\backend\gsl\parser.h(42): warning C4255: 'fnct': no function prototype given: converting '()' to '(void)'
3>C:\CraftRoot\labplot\src\backend\gsl\parser.h(53): warning C4255: 'func_t': no function prototype given: converting '()' to '(void)'
Comment 3 uwestoehr 2017-11-23 23:00:24 UTC
This is now fixed.