@The_Assimilator said:
For example, we do the backend while another vendor plugs their frontend code into ours.
So, they plug their front end into your backend? Sounds like you're buggered!
@The_Assimilator said:
For example, we do the backend while another vendor plugs their frontend code into ours.
So, they plug their front end into your backend? Sounds like you're buggered!
@The_Assimilator said:
it might return false if the floating-point values are of sufficiently large precision to not actually be equivalent
The value is so precise, it is not even equal to itself...
@AlexSolonik said:
if you set up your device to use a certain local IP, it will not be given that IP.
of course, it will not be given any IP, since it will not ask for one, it will just use the one you told it to use.
@AlexSolonik said:
Using your logic there, If I tell my laptop to use "192.168.0.101" What happens when I join a network in which that IP already exists? My laptop is either going to re-configure itself, or if I tell it not to do that, it simply won't be allowed to join the network.
I'm not saying it's necessarily a good idea to fix the IP (especially if it is a portable device that will be used on other networks), I agree that router was a pile of shite that I would have gotten replaced too. If you choose an IP that is already in use by another device, of course there will be a conflict, and the way that is handled probably depends on the OS. But there is no reason why you can't do this, the router will not "refuse to let it join the network" if it doesn't use DHCP.
@AlexSolonik said:
Your device can't just say "This is my IP" and be stubborn about it.
Of course it can, as long as it doesn't conflict with another device. DHCP is just a way to automatically assign IP addresses, no device is forced to use it if they don't want to.
@AlexSolonik said:
If another device tries to send that device data, they either use the IP the router assigned to that device, or the data won't be delivered.
If there was no DHCP request, there is no "IP the router assigned to that device", there is just the IP that was fixed, and the device is identified by that IP. The router will find where that IP is connected using ARP whether is was configured with DHCP, or manually.
@AlexSolonik said:
From my post: "It doesn't matter if the device requested a certain IP"
It doesn't matter if I fixed the IP on the device, the modem/router would give a random one.
But that doesn't make sense. If you fix the IP on the device, there is no DHCP request, why would it reconfigure itself with another IP?
@dhromed said:
I feel there is something insinuated by your code... but I can't quite put my finger on it.
I don't think you want to put your finger on it... unless you're into that kind of thing of course.
@Zemm said:
When I got phone banking with one of the biggest banks in Australia the password was 3 digits. I think mine was 791. I'm pretty sure they don't still do that. :)
Are you sure? By the way, what is your account number?
The Australian version also has more ingredients than the English/Irish - hydrolised soya AND protein, as opposed to just hydrolised soya protein.
@PJH said:
Assuming that sizeof(short) is two, which, of course, isn't necessarily a given, making the comment wrong. (It can be larger.)
Or smaller.