primary key / clustered index (unique) use for views

While reading this part of http://en.wikipedia.org/wiki/Index_(database)

Clustering re-orders the data block in the same order as the index, hence it is also an operation on the data storage blocks as well as on the index. Exact operation of database systems vary, but because the row data can only be stored in one order physically, only one clustered index can be created on a given database table. Clustered indices can greatly increase access speed, but usually only where the data is accessed sequentially in the same or reverse order of the clustered index, or when a range of items are selected.

So only one clustered index can be created on a given database table is limiting thus a view would allow for the same data to have a different clustered index.