There was a QT port in mozilla.org's CVS in the past, but it got dropped through lack of maintenance. While the four days it took to port the gfx layer is obviously impressive, it is a shame that all of the original work was allowed to bitrot.
If you are testing against a non-volatile value then there will be no side effects of the end of an if skipping following if statements that can't possibly be true. A decent optimising compiler will just jump to the end of the set of if statements.
However, as you say, it probably wouldn't turn the whole lot into a range check and a calculation.
Sorry, the technology to do much of this already exists. EMV allows for multi-application smart cards, but doesn't have the fingerprint technology and such.
The technology to do this already exists. The EMV specifications already allow for multi-application cards. This could already be done for payments but is not.
Visa and Mastercard don't make use of it for the simple reason of branding - you can't promote your brand with a generic looking card. In this day and age, company branding is more important than user convenience.
If you are in a crazy place which just wants to get something out the door as fast as possible, even if you do reviews they may be of little use (e.g. not much more than "does this meet the coding standard) or the reviewer may be pressured not to ask for rework because the insane management see no value in reworking code that does performs this month's cool feature, no matter how poorly implemented.
A positive outcome of this would be the complete and utter bankrupt of SCO.
I disagree. A threat to Linux is people being scared off by the lawsuit as happened to BSD (e.g. by Gartner) and I am pretty sure if SCO went bankrupt then another company could buy the remains and continue with the lawsuit.
Keeping to standards helps with future portability though, which I think is important to keep in mind. You say yourself "most" and not "all" compilers can support it. My own experience and Y2K just shows software tends to live longer than intended.
Thanks for the explanantion of why - I didn't know that.
... don't know how scope and for loops are supposed to mix...
Lint will catch that (almost certainly, but I have not checked), so you could try to make a clean Lint part of your coding standard or checkin requirements. If you can show whoever is in charge that the time spent Linting is more than recovered from the time spent fixing silly errors it should be a doddle to convince them. The only thing is, I think most projects need a list of lint warnings/errors that should be turned off for your situation, which goes into the configuration file your project will use. Guard this list with your sanity:)
Heh, I hate biometrics. If it can be copied, it's worthless.
I dread to think how you would copy goatse's anal print.
Any single security system would work better in conjunction with another. Your post reminded me of
this similar story story (also
duped) about using images as passwords. Assuming there was a limited set of mementos in an environment, you could use them as an index key and also as part of an auth system along with biometrics.
Thinking about it, it could make for decent security in some situations with people who do not use good passwords. It's obviously slower though.
And OT, captured signatures will go into decline as PIN transactions come in and then become the only customer verification method; customer not present fraud will be harder to get rid of though.
I went to a smart card exhibition for work and there was a lot of stuff about bio security such as retinal scans and fingerprints.
One thing we were told was that there are only so many unique features on the human body (I'm trying hard to remember exactly how many) and that one of them was in fact your anus print.
Everybody does rename by delete+create, or by
moving the repository file. No reason not
to automate it, methinks.
The first option obviously loses history, and I would have guessed the second would break old tags in your repository - I've not tried it, so does anybody know if that is correct?
Out of interest, how is Dreamweaver's standard compliance these days? I had heard before that it was not good (as in did not validate against the w3c thingy) and was wondering if it was better now?
Note: I may have heard lies, and did not check for myself. But I don't remember disagreements where I read it.
But tabbed browsing breaks the one-to-one link between views and windows. One window can have more than one view. In and of itself that's okay, except for the fact that no other application works like that. If I open two documents in TextEdit (for example), I get two windows.
gedit will open files in multiple tabs. Aside from that MDI was the way to go for a long time in the MS Windows world, before they decided that SDI was better. There are plenty of MDI applications out there, it's just not currently popular. But people have used them for years.
...when it provides no new functionality...
Tabs allow you to group related views, giving you an extra level of organisation over a single window per view.
Slashdot Mirror
Or looked at the past and saw their PC unit continually making losses?
There was a QT port in mozilla.org's CVS in the past, but it got dropped through lack of maintenance. While the four days it took to port the gfx layer is obviously impressive, it is a shame that all of the original work was allowed to bitrot.
If you are testing against a non-volatile value then there will be no side effects of the end of an if skipping following if statements that can't possibly be true. A decent optimising compiler will just jump to the end of the set of if statements. However, as you say, it probably wouldn't turn the whole lot into a range check and a calculation.
Code runs faster if you take out all possible white space between the instructions.
Sorry, the technology to do much of this already exists. EMV allows for multi-application smart cards, but doesn't have the fingerprint technology and such.
The technology to do this already exists. The EMV specifications already allow for multi-application cards. This could already be done for payments but is not.
Visa and Mastercard don't make use of it for the simple reason of branding - you can't promote your brand with a generic looking card. In this day and age, company branding is more important than user convenience.
If you aren't selling it, are you thinking of opening some or all of it?
So were Novell, except they played on being the good guys just before making product announcements involving Linux.
Actually, it was "I'd love a Segway" which sounds more nuptial to me.
If you are in a crazy place which just wants to get something out the door as fast as possible, even if you do reviews they may be of little use (e.g. not much more than "does this meet the coding standard) or the reviewer may be pressured not to ask for rework because the insane management see no value in reworking code that does performs this month's cool feature, no matter how poorly implemented.
And what has Eclipse got to do with servets? There's more to Java than GUI programs. Care to make any more meaningful sounding comments?
A positive outcome of this would be the complete and utter bankrupt of SCO.
I disagree. A threat to Linux is people being scared off by the lawsuit as happened to BSD (e.g. by Gartner) and I am pretty sure if SCO went bankrupt then another company could buy the remains and continue with the lawsuit.
That's what sells?
Reminds me of when I was at school and the new 5p pieces came out. Some enterprising individuals were selling them for 10p.
Keeping to standards helps with future portability though, which I think is important to keep in mind. You say yourself "most" and not "all" compilers can support it. My own experience and Y2K just shows software tends to live longer than intended. Thanks for the explanantion of why - I didn't know that.
... don't know how scope and for loops are supposed to mix ...
:)
Lint will catch that (almost certainly, but I have not checked), so you could try to make a clean Lint part of your coding standard or checkin requirements. If you can show whoever is in charge that the time spent Linting is more than recovered from the time spent fixing silly errors it should be a doddle to convince them. The only thing is, I think most projects need a list of lint warnings/errors that should be turned off for your situation, which goes into the configuration file your project will use. Guard this list with your sanity
Heh, I hate biometrics. If it can be copied, it's worthless.
I dread to think how you would copy goatse's anal print.
Any single security system would work better in conjunction with another. Your post reminded me of this similar story story (also duped) about using images as passwords. Assuming there was a limited set of mementos in an environment, you could use them as an index key and also as part of an auth system along with biometrics.
Thinking about it, it could make for decent security in some situations with people who do not use good passwords. It's obviously slower though.
And OT, captured signatures will go into decline as PIN transactions come in and then become the only customer verification method; customer not present fraud will be harder to get rid of though.
I went to a smart card exhibition for work and there was a lot of stuff about bio security such as retinal scans and fingerprints.
;)
One thing we were told was that there are only so many unique features on the human body (I'm trying hard to remember exactly how many) and that one of them was in fact your anus print.
I'd love to see goatse man's ID card
Everybody does rename by delete+create, or by moving the repository file. No reason not to automate it, methinks.
The first option obviously loses history, and I would have guessed the second would break old tags in your repository - I've not tried it, so does anybody know if that is correct?
Out of interest, how is Dreamweaver's standard compliance these days? I had heard before that it was not good (as in did not validate against the w3c thingy) and was wondering if it was better now? Note: I may have heard lies, and did not check for myself. But I don't remember disagreements where I read it.
But tabbed browsing breaks the one-to-one link between views and windows. One window can have more than one view. In and of itself that's okay, except for the fact that no other application works like that. If I open two documents in TextEdit (for example), I get two windows.
...when it provides no new functionality...
gedit will open files in multiple tabs. Aside from that MDI was the way to go for a long time in the MS Windows world, before they decided that SDI was better. There are plenty of MDI applications out there, it's just not currently popular. But people have used them for years.
Tabs allow you to group related views, giving you an extra level of organisation over a single window per view.
There was a report that QT support may be removed from Mozilla as it was not being maintained. I know that some volunteers stepped up but I don't know how it's going. I'm sure they would appreciate any help (QT newsgroup).
This is not flamebait, I am replying to myself to acknoledge that I made a stupid mistake....
:)
Are you setting up another reply to yourself?
Any reason why the article points at Mozilla's in-use Bugzilla rather than the Bugzilla project page?