Any language worth writing code in doesn't happily convert malformed strings into best guess integers without raising an error.
-
-
Replying to @marcan42
I'm not a fan of dynamic typing either, but was just trying to be constructive.
1 reply 0 retweets 0 likes -
Replying to @modrobert
This isn't about dynamic typing. Python is dynamically typed and doesn't have this problem. This is about PHP being horrible.
1 reply 0 retweets 0 likes -
Replying to @marcan42
Python can be horrible as well, ever dealt with 1 byte variables over a serial line? struct.unpack() horror?
1 reply 1 retweet 1 like -
Replying to @modrobert
Not sure what you're referring to. struct.unpack is cumbersome for large structured but there are better frameworks for that.
2 replies 0 retweets 0 likes -
Replying to @marcan42
When dealing with a serial device receiving 1 byte. The problem in general is more about this: http://stackoverflow.com/questions/41274864/declaring-a-single-byte-variable-in-python-3 …
1 reply 0 retweets 0 likes -
Replying to @modrobert
I'm still not sure where the problem is. Sure, Python doesn't have sized integer types by design. What is the actual problem?
1 reply 0 retweets 0 likes -
Replying to @marcan42
Dynamic typing; specifically regarding security, it sucks.
1 reply 0 retweets 0 likes -
Replying to @modrobert
Show examples, please. Are you sure you're not thinking of weak typing? PHP is weakly typed, Python is strongly typed.
1 reply 0 retweets 0 likes -
Replying to @marcan42
One example is the word press flaw mentioned in your initial tweet, it wouldn't be a problem with an integer.
1 reply 0 retweets 0 likes
It isn't a problem with properly implemented strong typing either. That would've never happened in Python.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.