Comments for DaVinci Unlimited Software

Comment on Turbo Pascal 1.0 Floppy by Pascal Fan

Pascal Fan — Wed, 07 Oct 2009 22:04:39 +0000

Fantastic!

I am a big fan of Pascal programming language. I still have the original boxes of Turbo Pascal 6 and Turbo Pascal 7. Borland Turbo Pascal inspired me to create Turbo51, Pascal compiler for 8051 microcontrollers.

Comment on WordPress and MediaWiki Integration by hit

hit — Mon, 08 Jun 2009 10:24:40 +0000

DaVinci Unlimited Software » Blog Archive » WordPress and MediaWiki Integration great article thank you.

Comment on WordPress and MediaWiki Integration by John Cheng

John Cheng — Tue, 12 May 2009 02:44:43 +0000

Hi there,
I would like to ask you for help on wordpress and mediawiki integration.
I have read Jon Davis’ article, but it seems that I still couldn’t make it to work.
My question is that I am able to get users’ names, but I am not able to get the users’ passwords. Maybe I should say that the “wordpress passwordhash” file doesn’t work as it suppose.

I am using wordpress 2.7 and mediawiki 1.14.

I know for sure that Jon’s script can connect to my wordpress database because the login script doesn’t complain user names at all, but passwords.

The error is that Login error
Incorrect password entered. Please try again.

I know this is because the passwordhash file is not working.

According to Jon’ article, he mentioned that we need to change our class-phpass.php location, which I did, but I just couldn’t make it to work.

I installed my mediawiki under wordpress and they share the same database.

the path looks like this:
/var/www/html/wordpress/mediawiki

and I set the path for the passwordhash like this:

require_once(’/direct/path/to/wordpress/wp-includes/class-phpass.php’)

require_once(’/var/www/html/wordpress/wp-includes/class-phpass.php’)

I know that you have had successful on integration for wordpress and mediawiki, so I would like to ask you for help.

I wondered if you could give me some directions on it.

Sincerely,

John Cheng

Comment on Turbo Pascal 1.0 Floppy by Jim McKeeth

Jim McKeeth — Mon, 16 Feb 2009 04:06:05 +0000

Wow, that is cool that you found one at your High School. Did you get to keep it? I think maybe I will frame mine or something. As you can see from the photo, my serial number is D3B0824362.

Comment on Turbo Pascal 1.0 Floppy by thehoove

thehoove — Mon, 16 Feb 2009 03:02:18 +0000

I actually found one of these when I was in high school… I think around 2005. Mine’s the same way, the the number is D3B0834097. Too bad I don’t have an old IBM to install it on…

Comment on Beyond Compare 3 Beta by Bookmarks about Beta

Bookmarks about Beta — Sat, 23 Aug 2008 07:00:47 +0000

[...] – bookmarked by 4 members originally found by MacDiva on 2008-08-02 Beyond Compare 3 Beta http://www.davinciunltd.com/2008/07/beyond-compare-3-beta/ – bookmarked by 4 members originally [...]

Comment on McAfee ScanAlert FAIL by blur

blur — Wed, 20 Aug 2008 23:06:28 +0000

Nice one, totally failure.

Comment on Turbo Pascal 1.0 Floppy by Troodon

Troodon — Mon, 21 Jul 2008 14:59:59 +0000

Do you, by any chance, have a copy of the original Turbo Pascal “Book license”? Thanks.

Comment on Genius Musicals by Randy

Randy — Wed, 16 Jul 2008 00:04:24 +0000

Hmm – looks like that link is pretty popular, as I can’t get through!

Comment on Order of Enum in Case Statement by Thaddy de Koning

Thaddy de Koning — Mon, 14 Jul 2008 08:28:25 +0000

Although the compiler always optimizes a case loop to be in-order,
Olivier is right: You also need to watch your algoritm.

That also implies that when you know some code is more likely to occur than other code in the case loop, you need to enforce it by evaluating from a low (the lowest) const value.

But that assumes the compiler will optimize from low to high, and that may not be the case: the compiler may also optimize high to low….
Some compilers do…

All in all, Olivier: it is pretty dangerous to rely on perceived optimizations that you can not be sure about and maybe version dependent.
In your case: you can better write out your algoritm in such a way that the optimization you want is enforced, i.e. f.e. by evaluating the most commonly encountered code first by means of if/then…/else /case/endcase