U++ forum: Welcome to the forum

Status & Roadmap

Authors & License

Funding Ultimate++

Search on this site

Search in forums

Home » U++ Library support » U++ Core » FIX: UPP::Scan returns int64 for INT_V

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Return to the default flat view

Create a new topic

Submit Reply

Re: FIX: UPP::Scan returns int64 for INT_V [message #32031 is a reply to message #32021]

Mon, 18 April 2011 10:46

kohait00 is currently offline

kohait00
Messages: 939
Registered: July 2009
Location: Germany

Experienced Contributor

i'm actually not using ValueTo..
it was merely of logical convenience. the stuff i'm pointing to is what i stumble upon, while dealing with environments where the data type issue is still a matter. i'm not planning to change upp to my will, don't get me wrong here.
to have a 'predictable' interface is another design feature.. thats why i said that, dealing with EditInt, i expect to be dealing with int, no matter which container it is actually in, dealing with EditDouble with double.. this is user POV.

i agree, that EditInt probably is not needed, due to same reason why float is not in Value (remember Smile

Smile

. it's a 'legacy', but here again, legacy means compatibility of types as well (as of me).

as of the SQL stuff. i think at this point, the data has been already analyzed and can continue to be dealt with as int, isnt it?

	if(m >= minval && m <= maxval) return int(m);//v; <====

the other changes in the files are, again, only for logical completeness..

Report message to a moderator

Send a private message to this user

[Message index]

		FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Wed, 13 April 2011 23:01
		Re: FIX: UPP::Scan returns int64 for INT_V By: Mindtraveller on Fri, 15 April 2011 21:44
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Sun, 17 April 2011 14:57
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Sun, 17 April 2011 21:23
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Mon, 18 April 2011 10:46
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Tue, 19 April 2011 07:28
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Wed, 27 April 2011 14:07
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Fri, 29 April 2011 20:17
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Mon, 02 May 2011 10:00
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Tue, 03 May 2011 11:04
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Fri, 06 May 2011 09:58
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Mon, 09 May 2011 18:06
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Fri, 13 May 2011 10:52
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Tue, 17 May 2011 11:08
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Tue, 17 May 2011 18:51
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Wed, 18 May 2011 11:14
		Re: FIX: UPP::Scan returns int64 for INT_V By: mirek on Wed, 18 May 2011 22:57
		Re: FIX: UPP::Scan returns int64 for INT_V By: kohait00 on Thu, 19 May 2011 09:35

Previous Topic:	Rect_<T>::SetNull not correct for Rectf (Rect_<double>)
Next Topic:	Ptr improve

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

PDF

]

Current Time: Wed Apr 30 03:46:16 CEST 2025

Total time taken to generate the page: 0.04499 seconds