Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » Bugs (& fixes) » Upp 12405 broken ?
Upp 12405 broken ? [message #53494] Mon, 06 April 2020 10:21 Go to next message
Didier is currently offline  Didier
Messages: 680
Registered: November 2008
Location: France
Contributor
Hello,

I downloaded the lastest version (12405) 2 days ago and it seems to be broken : lib/tiff does not compile (neither with CLANG nor with VC++ 2015)
uint16, uint23, ... tiff types seem to be ambiguas with Upp::uint16, uint32, ...

Didier


Re: Upp 12405 broken ? [message #53507 is a reply to message #53494] Tue, 07 April 2020 08:55 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 3356
Registered: August 2008
Senior Veteran
Hello Didier

I have just compiled all with CLANG and VC++2019 without problems.
In detail I have got even no warnings compiling libupp.cpp.
Could you specify the file and line that fails?


Best regards
IƱaki
Re: Upp 12405 broken ? [message #53541 is a reply to message #53507] Thu, 09 April 2020 23:02 Go to previous messageGo to next message
Didier is currently offline  Didier
Messages: 680
Registered: November 2008
Location: France
Contributor
Hello Koldo,

I have just seen the message, I will try to do a test case. Since you don't have any problems it's probably du to a include order problem or "using xxx" problem.

Anyway the types uint16, uint32, int16, int32, .... gets mixed up with the Upp::uint16, Upp::uint32, ...

I got this error after upgrading to the latest Upp version and upgrading my code version.
I don't have the problem under linux (Clang or GCC), but on windows I do.

I will give the exact messages tomorrow
Re: Upp 12405 broken ? [message #53584 is a reply to message #53541] Mon, 13 April 2020 19:34 Go to previous message
Didier is currently offline  Didier
Messages: 680
Registered: November 2008
Location: France
Contributor
Hello Koldo,

I finally looked into it, and as supected, it was an include order messing up with a 'using namespace Upp;'
So everything is fine Smile

[Updated on: Mon, 13 April 2020 19:35]

Report message to a moderator

Previous Topic: glut init-error.
Next Topic: Problem with MemorySanitizer
Goto Forum:
  


Current Time: Thu Apr 18 22:57:33 CEST 2024

Total time taken to generate the page: 0.03204 seconds