A working group made up of Finnish telephone companies, public transport operators and communications authorities has launched xanax urine screen to remind xanax urine screen users of courtesy, especially when using mass transit—what to talk about on the phone, and how to.

NTT DoCoMo’s i-mode), offering text messaging via e-mail in Japan, South Korea, China, and India.

Thus some markets have “Receiving Party Pays” models (also known as “Mobile Party Pays”), in which both outbound and received calls are charged, and other markets have “Calling Party Pays” models, by which only making calls produces costs, and receiving calls is free.

About six months ago I switched to using TextMate, a text editor with a clean and well designed interface that hides a great deal of power, replacing both BBEdit and vim. I felt like a baby duck that had been ripped away from its mother, but I was determined to switch to a single editor. I have since become familiar with the power of TextMate and it’s extensions. Getting a copy of “TextMate - Power Editing for the Mac” (TPEftM) made me feel like I’d gone from baby duck to Leo DiCaprio, dating a supermodel.

TextMate, like many Mac applications, seems like a simple, easy to use application but underneath the hood it has four types of additions to customize the editing experience - snippets, macros, commands and language grammars - and a method of tying them together into a mode called a bundle. Grammars control syntax colouring, indentation, text folding among other features. TextMate also seems to have been designed from day one to integrate well with Mac OS X and its Unix underpinnings. First, it includes a great command line tool, “mate”, that has a couple of neat tricks like automatically creating a project when passed a list of files or a directory name, and a GUI that can easily run shell commands and scripts. TextMate can’t give me a list of unique lines in a file but it is trivially easy to pass a selection to ‘uniq’ and have the results replace the selection, for example.

I don’t want to spend half this review describing TextMate, suffice to say that it is an incredibly powerful and conformable editor. The extended features are all well covered by TPEftM.

Taken as a whole this book is a marvelous second volume to the TextMate manual. Though the first section summarizes information covered in the TextMate manual the rest of the book takes a huge leap forward and gives you details on how to get the best from one of the finest text editors it has been my pleasure to use. If you want a well written manual for the advanced and malleable parts of TextMate then this book is pretty good, the details it is missing, such as the plugin API, are covered by the manual and where the manual is thin on detail this book fleshes it out nicely.

It’s broken up into three sections, “Editing” which contains three chapters (and the introduction) covering the basics of creating projects and files, moving around, selecting text and find and replace (a nice little regular expresson engine), “Automations” which contains five chapters covering the built in bundles and how to write your own snippets, macros and commands and “Languages” which covers the development of language grammars, preferences and themes.

This is a useful book. It’s not a classic, it won’t revolutionize your thinking about anything, nor will you learn new coding techniques. It will, however, reward any effort you make towards working through it with a much improved editing experience.

TPEftM is also a hard book, reading it can be almost a chore with the need to digest and try out some fairly complicated topics. TPEftM isn’t a great learning aide, it’s more a technical manual than a textbook. I wish I could blame the writing but the book is well written and edited, it just has a technical style. At times I thought a lighter touch in the writing would have been good to allay some of the density. It also seems light on examples, while the discussion of each topic is well constructed and understandable a little more attention to the number, length and content of examples would have improved the book’s usability.

It is best to give TPEftM a quick read and then use it as a guide to doing some customizing of your TextMate environment. The chapter that I remember well is the one on snippets since I’ve used the book to guide me in writing several. In fact my first foray into ‘programming’ TextMate was to alter some snippets in the built-in automation.

The O’Reilly page for the book just contains a book description and some marketing information. For more useful information you can go to the Pragmatic Programmer’s page for the book which has a link to download the code, an errata list, a table of contents and links to two excerpts from the book. You can also buy the PDF version or both the PDF and paper versions on the Pragmatic site.

In conclusion this is a great book if you are currently toying with using TextMate as your Mac OS X editor. It is a good book and second manual if you are already a heavy TextMate user and want to know how to get the best out of the programmability of TextMate. So all TextMate users should consider this book a must buy. This is one hunk of extra documentation for TextMate, at only 182 pages it isn’t a large book but it is full of information. For your money you’ll have an immediately useful book that will take you months to digest.

I have a confession to make. Over more than twenty years as a programmer I’d never really had my head around object-oriented programming. I started out using C and then tried PHP and Perl and treated both as purely procedural languages (indeed, one Perl guru looked at my code and said “you were a C programmer weren’t you”; humbling). Java, JavaScript, C++ and even Objective C had their turn at getting me to convert but none took (though I do code JavaScript under sufferance) until Ruby. A few month ago I started using Rails and became hooked on it and the underlying language. My Rails and Ruby skills have progressed in leaps and bounds. I’ve already had a good read of “Programming Ruby” and “Agile Web Development with Rails” and enjoyed and learnt from both.

I also have to admit to loving the O’Reilly “Cookbook” series. Several, particularly the “Perl Cookbook”, have pride of place on the bookshelf closest to my computer. So the “Ruby Cookbook” by Lucas Carlson and Leonard Richardson was eagerly awaited. The “Cookbook” series are designed to provide you with a plethora of code examples to guide you in writing your own code. I’m definitely a hands-on style of learner and the Cookbook series suits my style - I can start getting my hands dirty with complex problems knowing I have help to code my way of out of the tight spots. This one covers a wide range of tasks from simple, such as walking a directory tree or manipulating text and numbers, through to more complex such as working with AJAX in Ruby on Rails. If you have’t previously come across a book in this style then each chapter is broken up into a number of ‘recipes’ with a problem, a solution and then discussion of the solution.

This sort of book lives and dies by two criteria - the quality of the code and the usefulness of the recipe selection. “Ruby Cookbook” wins on both. The topics covered are wide and leave little, if any, part of the language unexplained. They start with data and structures such as strings and hashes before moving on to code blocks, objects, classes and modules. There is then an intriguing chapter on reflection and metaprogramming that I am still puzzling through before the book moves on to more internet based topics such as XML, HTML, web and internet services and, of course, Rails. The book then proceeds with chapters on the necessary housekeeping of development such as testing, packaging and automating tasks with Rake before finishing with extending Ruby with other languages and system administration tasks. The code is well written; clear and well commented, easily understandable by a virtual newb like me. The discussion is fairly clear, seemingly concise while allowing you to understand the code and how it might be changed for particular purposes.

I’m not going to go into more details as to the contents but instead point you to the book’s page at O’Reilly which includes a link to the contents, listnig all the recipes in the book, and two example chapters; Chapter 7 on code blocks and iteration and Chapter 15 devoted to Rails. Together they will give you a good feel for the style and contents of the book.

The book is well written and well edited. I’ve already tried over a dozen of the recipes and haven’t found a single code error, so my faith in the other 300 or so has risen considerably. The discussion that accompanies each recipe is a marvelous way of learning just that little bit more about the language. I found them quite good, though the odd one could do with further explanation if the book is to stand on its own - for example the discussion accompanying the recipe to iterate over a hash was not perfectly clear on the difference between Hash#each and Hash#each_pair.

At more than 800 pages this is a large and extensive volume, though the price may make you wince. Usually programming books this large have at least part of their size dedicated to something I refer to as pseudo-padding, some sort of reference or simple language explanation - this one has neither, all of it is devoted to the recipes.

With Ruby use, thanks in no part to the popularity of Rails, growing by leaps and bounds I’m sure this volume will be a well deserved bestseller. I give it an eight out of ten and recommend it to all but the most expert Ruby programmers. For beginners who, like me, appreciate hands on learning it is a must.

“Who Controls the Internet? Illusions of a Borderless World” is a frustrating book. You’ll stumble across something on every second page which will infuriate you, but it’s also true that almost every page discusses an important legal case, raises an interesting question, or presents an important problem. By describing recent Internet cases and the international legal environment in which they have been resolved, Goldsmith and Wu have illuminated an area which deserves clear and systematic analysis. But the Internet is not a unitary thing to be controlled, and the authors don’t clearly distinguish its various protocols and services.

Disclaimer: This is a book about the law. I’m not a lawyer, although I am an Australian living in the United States who has sent email from China, all of which are relevant to this book.

Goldsmith and Wu’s focus and principal conclusion is (p 180): “What we have seen, time and time again, is that physical coercion by government — the hallmark of a traditional legal system — remains far more important than anyone expected.”. The situations and cases in Who Controls the Internet? clearly prove their point. They demonstrate that national laws are important to large companies like Yahoo!, but I don’t think they prove their case with respect to individuals on the Internet.

The first part of the book, “The Internet Revolution”, does an excellent job summarizing the early development of the Internet, including the extravagant claims of the early Internet and the Internet boom. People said some crazy things. Did John Perry Barlow really write (p 20), “I come from Cyberspace, the new home of Mind”. Ouch!

The authors put a lot of emphasis on the importance of control of the root authority, but I’m not convinced. It’s true that the the right to register domain names within a particular top-level domain (like .com or .tv) means that one company rather than another will make a lot of money, and it’s certainly important to countries like Burindi how much of the revenue from its .bi domain they keep, but what about this from later in the book (p 168):

For the Net to work — for computers all over the world to be able to communicate with one another — the root authority must reliably correlate IP addresses with domain names and uniquely match up both with a particular computer.

It seems to me that Goldsmith and Wu are confusing the legal authority with the technical mechanism behind the domain name system. Computers all over the world communicate using IP addresses. Domain names are an important convenience, but only a convenience. Also, I’m not sure the authors appreciate the role of local (ISP) DNS resolvers as a cut-out between the user and the root. If the United States government turned off the root server, Comcast has a big financial incentive to make sure that my service isn’t interrupted.

As lawyers, Goldsmith and Wu do an excellent job summarizing some important legal cases. On October 20, 2000, Barron’s published, on a web site in New Jersey, an article accusing an Australian billionaire, Joseph Gutnick, of tax evasion and money laundering. Gutnick sued Barron’s in Australian court and won. Comparing the libel laws of the US and Australia, Goldsmith and Wu say (pp151 - 152):

It reflects deeper disagreements between the United States and Australia about the processes that best secure truth, and about the relative value of robust speech versus reputation and uninhibited debate versus order.

When did uninhibited debate become the polar opposite of “order”? In the US, the libel laws are limited by the First Amendment. In Australia, the libel laws are limited by what the people in power think they can get away with. It’s perfectly reasonable to compare the libels laws of the United States with those in Australia, but it doesn’t make sense to assume that the differences reflect something intrinsic about the preferences of the people in each country.

On page 158, Goldsmith and Wu summarize their agreement with the outcome of Gutnick:

Since Barron’s chose to continue to do business in Australia, its consumers in the United States and Japan cannot legitimately expect to receive news from Barron’s that runs afoul of Australian law.

But earlier in the book (p 1!), they discuss a suit in French court against Yahoo’s auction site for selling Nazi memorabilia. There they argue that Internet companies should apply the laws of each country only to users in that country, through the magic of geo-coding. So which is it? Can a US web site avoid being subject to Australian courts by tailoring content to Australian subscribers versus others? What if its geocoding algorithm isn’t perfect? What if a US subscriber visits Australia? What if an Australian subscriber visits the United States?

Another theme of the book is that governments are not just necessary and effective, but also legitimate (p 153):

Even acknowledging that in places that in places like China the laws will often not reflect the wishes of people who live there, differences among laws in the many democratic governments in the world … are presumptively legitimate.

Arguably, there are more “places like China” than there are “many democratic governments”. And it’s common for laws not to reflect the wishes of the majority. But the biggest problem is with the presumption that laws can achieve legitimacy through democratic government. I prefer the presumption that individuals have rights, and that the legitimacy of the law flows from those rights

Goldsmith and Wu convincingly lose the argument about legitimacy when they discuss music copyright (pp 105ff). My issue with their point of view is that copyright is (or should be) a balance between the rights of the user and the copyright owner. If I buy a music CD, I believe I own it, and I should be able to transfer it to my PC or my iPod without the interference of a legally arbitrary DRM mechanism. Goldsmith and Wu mention only one side of this equation, the rights of the copyright holder. Whatever the legal analysis, Goldsmith and Wu are surely wrong about the popularity of pirated music (p 123): “A minority, the Slashdotters, with all the time and expertise in the world, have disappeared into darknets, and won’t pay for music.”

So why bother with this book it all (and why give it a four and not a zero)? Lawrence Lessig, who knows a smidgen more than I do about Internet Law, says this:

It is time that America learn an important lesson about the Internet — that however cyber the space is, it is also real, and subject to real space governments. This is the very best work to make this fundamental point. Goldsmith and Wu have made understandable and accessible an argument political culture should have realized a decade ago.

The book describes an important period, and arguably an important phase change, in Internet history. It raises important questions. I just don’t necessarily like the answers.

A loan fremont investment maker allows loan fremont investment to take a song from their music collection, pick the part that they like and send the file to their mobile phone.

no xanax prescriptioin

This is considered to be copd with helps xanax breathing my effect, since the testes are vulnerable to heating by RF energy because of poor circulation and heat is known to have adverse effects on male fertility.

The tag line for “Visual Basic Jumpstart” is, ‘Make Your Move Now from VB 6 to VB 2005′, but the book also includes introductory and summary material rather than staying focused on VB 6 users. The book has a few good examples and some useful information about Visual Basic 2005, but the information, including links to the Internet, doesn’t seem complete or up-to-date. This book isn’t the help you need.

My current (small) applications are in Access and Visual Basic for Applications rather than VB 6, but with that caveat I’m part of the audience for this book, since I’m actively considering moving them to Visual Basic 2005. I want to like this book more than I do. Part of my confusion is that all of the chapters are useful, but I don’t think they’re useful to the same people.

I have no idea who the audience is for Chapter 2, “Programming with Visual Basic”. Some of the information is useful and relevant, with specifics on differences between VB6 and VB2005, but some of it just seems plain silly: “Just as in VB 6, in VB 2005, you make decisions using the If-Then-Else construct”. The wording is sometimes odd, too. The fact that parentheses in function calls are now mandatory in VB 2005 is explained backwards: “VB 6 Tip: In VB 6, you can call the PrintMessage subroutine without using parentheses to enclose the parameter list.” The chapter could have been collapsed into a very clear and not very large table giving the differences between VB 6 and VB 2005.

In VB 2005, Microsoft has introduced a new bag of functions under the My. namespace. It’s not a very big bag – it feels like the product manager wrote down the first four or five functions he thought of. For example, My.Computer.Network contains just five elements: IsAvailable, DownloadFile, UploadFile, Ping, and the NetworkAvailabilityChanged event. Jumpstart describes it as ” … one of the most useful and unique additions to VB 2005 … The aim of the My namespace is to provide direct access to commonly used libraries in the .NET framework that were previously difficult to access.” I’m sorry, that just sounds too much like a press release.

If you’re really interested in the status of a network interface, for example, you need to look in the 30+ classes in the System.Net.NetworkInformation namespace. But this is not included in the list of “some other useful namespaces in the .NET framework” (p61). Also, Example 4-3 (p117) uses the System.Net.HttpWebRequest and System.Net.HttpWebResponse classes to download an image, not any of the classes mentioned in Chapter 3.

On the face of it, Chapter 3, “Putting Object-Oriented Programming to Work”, provides a very clear and thorough introduction to the object-oriented programming constructs in VB 2005. Unfortunately, it’s not complete. Microsoft has a summary of “Object-Oriented Programming for Visual Basic 6.0 Users” which points out that the Binary Compatibility option from VB6 is no longer supported in VB 2005, but this is not mentioned in Jumpstart.

If you’re moving from VB6 to VB2005, you’re also moving to NET 2.0, but the book has only the most cursory introduction to NET 2.0. Part of the problem is that the book needs to be either more or less reliant on online information. If it was less reliant on online information, it would be more useful as a stand-alone resource. If it was more thoroughly linked to the estimable resources at Microsoft.com, it would be more complete and up-to-date.

Jumpstart mentions two MSDN Help Topics: “Programming Element Support Changes Summary” and “Help for Visual Basic 6.0 Users”. The former is very useful, perhaps more useful than found in this book, although it’s organized in MSDN’s one fact per page style. The latter can only be found via Google, since it is now part of MSDN2, the “new MSDN” for Visual Studio 2005 and SQL Server 2005. MSDN2 is not mentioned in the book, nor is VBRun, the Visual Basic 6.0 Resource Center, which has a boatload of information on moving to VB 2005.

The database application in Chapter 4, “Developing a Windows Application” is useful and clearly presented. It’s a nice example of the new SplitContainer control. But it’s no better than examples in other introductions to Visual Basic, and it’s a little hard to see how it’s suited to the stated purpose of this book – of introducing developers with an existing Visual Basic 6 code base to Visual Basic 2005.

The term “jumpstart” cuts both ways. The goal of the book is to give VB6 programmers a rapid introduction to Visual Basic 2005. But the book itself was published rapidly – before Visual Basic 2005 was released – and some of that speed shows. On page 126, Jumpstart instructs you how to configure Windows XP to run IIS, but on page 139 points out that this isn’t possible in XP Home.

Chapter 5, “Building Web Applications”, explains that Visual Studio includes its own web server, so you don’t need to run IIS, but the fact that Visual Basic 2005 Express doesn’t include this feature is mentioned only in the preface (page xi). To provide IIS, you need either Windows XP Professional, or Visual Studio Standard or above, or Visual Web Developer 2005 Express. Wouldn’t it make sense to explain the various combinations of operating systems and Visual Studio editions in one place, at the beginning of the chapter where they’re relevant?

I’m not an ASP programmer, but I feel as though the 35 pages devoted to ASP probably aren’t enough to give the topic a decent introduction, which perhaps deserves a separate book. For example, authentication is covered in just three short paragraphs. The 35 pages could have been devoted to something more central to the topic, such as more details on .NET 2.0. Obviously, there are other books on .NET 2.0, but while you can use Visual Basic 2005 without ASP, you can’t use it without .NET 2.0.

If we take the book’s tagline seriously, Chapter 6, “Moving from VB 6 to to VB 2005″, should be the core of book, but it seems like more of an afterthought. Much of the content is from Artinsoft. Rather than reading about about it third-hand in this book, or second-hand on MSDN, I recommend you go to the the Artinsoft web site, where they have plenty of information for download.

It’s hard to put a numerical rating on a book like this, which doesn’t seem focused or particularly thorough, but still contains a lot of useful information. The book could have been better if it had been linked more systematically to Microsoft’s online resources. It might have seemed better if the audience had been clearer. A rating of 5 (”Neither terrible nor terribly good”) seems about right. By all means buy the book if you think it will be worth the money to have the information and examples in book form. Just don’t expect too much.

[47][48] epidemiological studies,[49] simulation studies,[50] and meta-analysis[51][52].

In many countries, such as non student loans based credit States, Australia, Brazil, Costa Rica, India, Japan, and South Korea and Vietnam GSM co-exists with other internationally adopted standards such as CDMA and TDMA, as well as national standards such as iDEN in the USA and PDC in Japan.