OpenLLM-France/wikimedia huggingface dataset:
# Economic Sophisms/35

<pagequality level="4" user="Zoeannl" />style="background: #ececec; text-align: left; padding-left: 0.5em; font-weight: bold;" class="table-rh"But what is true with regard to sugar, cannot be otherwise with regard to bread. If, then, the utility of any branch of industry is to be estimated not by the amount of satisfactions it is fitted to procure us with a determinate amount of labour, but, on the contrary, by the amount of labour which it exacts in order to yield us a determinate amount of satisfactions, what we ought evidently to desire is, that each acre of land should yield less corn, and each grain of corn less nourishment; in other words, that our land should be comparatively barren; for then the quantity of land, capital, and manual labour that would be required for the maintenance of our population would be much more considerable; we could then say that the demand for human labour would be in direct proportion to this barrenness. The aspirations of MM. Bugeaud, Saint-Cricq, Dupin, and d'Argout, would then be satisfied; bread would be dear, labour abundant, and France rich—rich at least in the sense in which these gentlemen understand the word.
What we should desire also is, that human intelligence should be enfeebled or extinguished; for, as long as it survives, it will be continually endeavouring to augment the proportion which the end bears to the means, and which the product bears to the labour. It is in that precisely that intelligence consists.
Thus, it appears that sisyphism has been the doctrine of all the men who have been intrusted with our industrial destinies. It would be unfair to reproach them with it. This principle guides Ministers only because it is predominant in the Chambers; and it predominates in the Chambers only because it is sent there by the electoral body, and the electoral body is imbued with it only because public opinion is saturated with it.
I think it right to repeat here that I do not accuse men such as MM. Bugeaud, Dupin, Saint-Cricq, and d'Argout of being absolutely and under all circumstances sisyphists. They are certainly not so in their private transactions; for in these they always desire to obtain by way of exchange what would cost them dearer to procure by direct production; but I affirm they are sisyphists when they hinder the country from doing the same thing.
# Economic Sophisms/36

<pagequality level="4" user="Zoeannl" />style="background: #ececec; text-align: left; padding-left: 0.5em; font-weight: bold;" class="table-rh"
IT has been said ... but in case I should be accused of putting sophisms into the mouths of the protectionists, I shall allow one of their most vigorous athletes to speak for them.
"It has been thought that protection in our case should simply represent the difference which exists between the cost price of a commodity which we produce and the cost price of the same commodity produced by our neighbours.… A protective duty calculated on this basis would only ensure free competition …; free competition exists only when there is equality in the conditions and in the charges. In the case of a horse race, we ascertain the weight which each horse has to carry, and so equalize the conditions; without that there could be no fair competition. In the case of trade, if one of the sellers can bring his commodity to market at less cost, he ceases to be a competitor, and becomes a monopolist.… Do away with this protection which represents the difference of cost price, and the foreigner invades our markets and acquires a monopoly."
"Every one must wish, for his own sake, as well as for the sake of others, that the production of the country should be protected against foreign competition, whenever the latter can furnish products at a lower price."
This argument recurs continually in works of the protectionist school. I propose to examine it carefully, and I solicit earnestly the reader's patience and attention. I shall consider, first of all, the inequalities which are attributable to nature, and afterwards those which are attributable to diversity of taxation.
In this, as in other cases, we shall find protectionist theorists viewing their subject from the producer's stand-point, whilst we advocate the cause of the unfortunate consumers, whose interests they studiously keep out of sight. They institute a
* ↑ M. le Vicomte de Romanet.
* ↑ Matthieu de Dombasle.
# Economic Sophisms/37

<pagequality level="4" user="Zoeannl" />style="background: #ececec; text-align: left; padding-left: 0.5em; font-weight: bold;" class="table-rh"comparison between the field of industry and the turf. But as regards the latter, the race is at once the means and the end. The public feels no interest in the competition beyond the competition itself. When you start your horses, your end, your object, is to find out which is the swiftest runner, and I see your reason for equalizing the weights. But if your end, your object, were to secure the arrival of some important and urgent news at the winning-post, could you, without inconsistency, throw obstacles in the way of any one who should offer you the best means of expediting your message? This is what you do in commercial affairs. You forget the end, the object sought to be attained, which is material prosperity; you disregard it, you sacrifice it to a veritable petitio principii; in plain language, you are begging the question.
But since we cannot bring our opponents to our point of view, let us place ourselves in theirs, and examine the question in its relations with production.
I shall endeavour to prove,
1st, That to level and equalize the conditions of labour, is to attack exchange in its essence and principle.
2d, That it is not true that the labour of a country is neutralized by the competition of more favoured countries.
3d, That if that were true, protective duties would not equalize the conditions of production.
4th, That liberty, freedom of trade, levels these conditions as much as they can be levelled.
5th, That the least favoured countries gain most by exchange.
I. To level and equalize the conditions of labour is not simply to cramp exchanges in certain branches of trade, it is to attack exchange in its principle, for its principle rests upon that very diversity, upon those very inequalities of fertility, aptitude, climate, and temperature, which you desire to efface. If Guienne sends wine to Brittany, and if Brittany sends corn to Guienne, it arises from their being placed under different conditions of production. Is there a different law for international exchanges? To urge against international exchanges that inequality of conditions which gives rise to them, and explains them, is to argue against their very existence. If protectionists had on their side
# Economic Sophisms/4

<pagequality level="0" user="Londonjackbooks" />
# Economic Sophisms/31

<pagequality level="4" user="Zoeannl" />style="background: #ececec; text-align: left; padding-left: 0.5em; font-weight: bold;" class="table-rh"upon this principle, we may assert that the effort of mankind at large is to obtain, for their own benefit undoubtedly, bread and all other products cheaper, to lessen the labour needed to procure a given quantity of what they want.
This incontestable tendency of mankind once established, should, it would seem, reveal to the legislator the true principle, and point out to him in what way he should aid industry (in as far as it falls within his province to aid it); for it would be absurd to assert that human laws should run counter to the laws of Providence.
And yet we have heard M. Bugeaud, as a deputy, exclaim: "I understand nothing of this theory of cheapness; I should like better to see bread dearer and labour more abundant." And following out this doctrine, the deputy of the Dordogne votes legislative measures, the effect of which is to hamper exchanges, for the very reason that they procure us indirectly what direct production could not procure us but at greater expense.
Now, it is very evident that M. Bugeaud's principle as a deputy is directly opposed to the principle on which he acts as an agriculturist. To act consistently, he should vote against all legislative restriction, or else import into his farming operations the principle which he proclaims from the tribune. We should then see him sow his corn in his most sterile fields, for in this way he would succeed in working much to obtain little. We should see him throwing aside the plough, since hand-culture would satisfy his double wish for dearer bread and more abundant labour.
Restriction has for its avowed object, and its acknowledged effect, to increase labour.
It has also for its avowed object, and its acknowledged effect, to cause dearness, which means simply scarcity of products; so that, carried out to its extreme limits, it is pure sisyphism, such as we have defined it,—labour infinite, product nil.
Baron Charles Dupin, the light of the peerage, it is said, on economic science, accuses railways of injuring navigation; and it is certain that it is of the nature of a more perfect, to restrict the use of a less perfect means of conveyance. But railways cannot hurt navigation except by attracting traffic; and they
# Economic Sophisms/38

<pagequality level="4" user="Zoeannl" />style="background: #ececec; text-align: left; padding-left: 0.5em; font-weight: bold;" class="table-rh"sufficient logic and power, they would reduce men, like snails, to a state of absolute isolation. Moreover, there is not one of their sophisms which, when submitted to the test of rigorous deductions, does not obviously tend to destruction and annihilation.
II. It is not true, in point of fact, that inequality of conditions existing between two similar branches of industry entails necessarily the ruin of that which is least favourably situated. On the turf, if one horse gains the prize, the other loses it; but when two horses are employed in useful labour, each produces a beneficial result in proportion to its powers; and if the more vigorous renders the greater service, it does not follow that the other renders no service at all. We cultivate wheat in all the departments of France, although there are between them enormous differences of fertility; and if there be any one department which does not cultivate wheat, it is because it is not profitable to engage in that species of culture in that locality. In the same way, analogy shows us that under the régime of liberty, in spite of similar differences, they produce wheat in all the countries of Europe; and if there be one which abandons the cultivation of that grain, it is because it is found more for its interest to give another direction to the employment of its land, labour, and capital. And why should the fertility of one department not paralyze the agriculturist of a neighbouring department which is less favourably situated? Because the economic phenomena have a flexibility, an elasticity, levelling powers, so to speak, which appear to have altogether escaped the notice of the protectionist school. That school accuses us of being given up to system; but it is the protectionists who are systematic in the last degree, if the spirit of system consists in bolstering up arguments which rest upon one fact instead of upon an aggregation of facts. In the example which we have given, it is the difference in the value of lands which compensates the difference in their fertility. Your field produces three times more than mine. Yes, but it has cost you ten times more, and I can still compete with you. This is the whole mystery. And observe, that superiority in some respects leads to inferiority in others. It is just because your land is more
# Futurebasic/Language/Reference/on appleevent
## ON APPLEEVENT
### Statement

(+) Appearance (+) Standard Console

### Revised

May, 2001 (Release 5)

### Description

AppleEvents are used for communication between applications. (In dealing with Apple Events, you will often see applications referred to as processes.) Use this FB statement to set up and track specific types of Apple Events. Event types and classes that are to tracked are part of the ON APPLEEVENT parameters. Types and Classes Apple events are divided into general groups called Types. Those groups are subdivided into specific classes. As an example, you may have heard of Apple core events. There are events which every application should understand and handle. The class for this group is called _coreEventType. the long integer constant for this type is _"core". Either of these two forms of address is acceptable in FB, but only one (_"core") is case sensitive. If you wanted to deal with core events, you would have to tell the Apple Event Manager which of four classes might be of interest. As an example, you might want to know if the Finder (or some other process) sent a message to you to open a document. In such a case the class would be _kAEOpenDocuments or _"odoc". An event handler set up for this type and class would be entered as follows:
FB recognizes a special event class of _"TEXT". When this class in encountered, the contents of the event parameter may be more easily accessed using the APPLEEVENTMESSAGE$ function. The following simple example shows how your ON APPLEEVENT handler might look for incoming text.
It is often convenient to pass large blocks of data via Apple Events as handles. FB processes this automatically by pulling the data from the Apple Event and transferring it to your application as a handle. FB always copies the data, so when you are finished, you must manage disposal on your own. The following fragment shows how a handle is received and disposed. To show that the data was accepted, this routine prints the first fifty characters of the handle as ASCII text.
When this handler was set up, the class parameter for ON APPLEEVENT was _"CLAS". You can see that it was required for use in FN AEGETPARAMDESC. Note: Some handlers (like the example above) are already built in to most of the FB runtimes. In order to override a behavior, you will first have to use KILL APPLEEVENT. Only one Apple Event vector is allowed. If you create multiple ON APPLEEVENT vectors, each one overwrites the previous, so the last vector will be used. To handle multiple eventClasses and/or types in the one application, set up a vector for each, pointing all to the one handler. The handler can determine which class it has received by examining the global variable gFBAEType&. (See KILL APPLEVENT for the proper method of replacing an event vector.)
Example:

### See Also

SENDAPPLEEVENT, HANDLEEVENTS, APPLEEVENTMESSAGE$, GETPROCESSINFO, KILL APPLEEVENT
# Futurebasic/Language/Reference/on break
## ON BREAK
### Statement

(+) Appearance (+) Standard Console

### Description

This statement designates a particular function or subroutine as a break-event handling routine. A break-event handling routine is called in response to a cmd-period keypress by the user. After a cmd-period keypress event occurs, FB does not call your designated routine immediately. Instead, your program continues executing until it reaches a HANDLEEVENTS statement; at that time, HANDLEEVENTS will call your designated routine. If the user presses cmd-period but you have not designated any break-event handling routine, your program continues executing until a HANDLEEVENTS is reached; FB then displays an alert asking the user whether to continue or to stop. If the user elects to stop, FB next calls your "stop-event" handling routine, if any (see ON STOP); and then your program stops. If the user elects to continue, the program continues executing at the first statement following the HANDLEEVENTS. One common use for a break-event handling routine is to prevent the user from stopping your program by means of cmd-period.
Your routine can be as simple as this:
This function does nothing, but if you designate it in an "ON BREAK FN DoBreak" statement, then cmd-period keypresses will be "routed" to this function rather than causing the "Stop or Continue" alert to be displayed.
Note:
If you use the ON BREAK FN userFunction syntax, then userFunction must refer to a function which was defined or prototyped at an earlier location in the source code. Your break-event handling function should not take any parameters, nor return a result.

### See Also

HANDLEEVENTS; ON STOP; TRON X
# Futurebasic/Language/Reference/octstring
## OCT$
### Function

(+) Appearance (+) Standard (+) Console

### Description

This function is a string of octal (base-8) digits which represent the integer value of expr. The returned string will consist of either 3, 6 or 11 characters, depending on which of DEFSTR BYTE, DEFSTR WORD or DEFSTR LONG is currently in effect.
Note that if the value of expr is too large to fit in the currently selected DEFSTR size, the string returned by OCT$ will not represent the true value of expr. In FB, integers are stored in standard "2's-complement" format, and the values returnet by OCT$ reflect this storage scheme. You need to keep this in mind when interpreting the results of OCT$, especially when expr is a negative number.
For example:
Note: To convert a string of octal digits into an integer, use the following technique: ÊÊÊintVar = VAL&("&o" + octalString$) intVar can be a (signed or unsigned) byte variable, short-integer variable or long-integer variable. See Appendix C: Data Types and Data Representation, to determine the range of values that can be stored in different types of integer variables.

### See Also

HEX$; BIN$; DEFSTR BYTE/WORD/LONG; VAL&
# Futurebasic/Language/Reference/offsetof
## OFFSETOF
### Function

(+) Appearance (+) Standard (+) Console

### Description

Use this function to find where a particular field begins within a record. OFFSETOF returns the field's offset as a number of bytes past the beginning of the record. In the first syntax, recordType is the name of a "true record" type as defined in a BEGIN RECORD statement; trueRecVar is a variable declared as a "true record" type; fieldName is the name of a field within that "true record" type. In the second syntax, const is a symbolic integer constant, without its leading underscore character. Typically, this will be a constant which was defined within a DIM RECORD...DIM END RECORD block. pseudoRecVar.recLen is a "pseudo-record" variable declared as DIM psuedoRecVar.recLen. When you use the second syntax, OFFSETOF just returns the value of const. Because a symbolic constant always has a global scope, the IN pseudoRecVar clause is not required. The value passed as fieldName is seen by the compiler as a constant. You do not use type designator suffixes like $,&,#, etc.

### See Also

SIZEOF; TYPEOF; BEGIN RECORD; DIM RECORD; Appendix C: Data Types and Data Representation
# Futurebasic/Language/Reference/mouse position
## Syntax

buttonStatus = MOUSE(_down)

## Description

If your program does not do any kind of event-trapping using the HANDLEEVENTS statement, then you can use the MOUSE(_down) function to determine whether the mouse button is currently down. In these circumstances, MOUSE(_down) returns _zTrue is the button is down, or _false otherwise.
The MOUSE(_down) function will not work if your program traps events using HANDLEEVENTS. Since most well-designed programs trap events this way, the MOUSE(_down) function is probably of limited usefulness. See the <a href="mouse%20event.html">MOUSE <event></a>functions to learn how to respond to mouse clicks using event trapping.
Note: You can also use the Toolbox function FN BUTTON to determine whether the mouse is currently down. FN BUTTON works regardless of whether your program uses event trapping.

## See Also

MOUSE <position> MOUSE <event>ON MOUSE
# Futurebasic/Language/Reference/not
## NOT
### Description

The NOT operator interprets expr as an integer, and returns another integer in whose internal bit pattern all the bits are flipped to their opposite state (i.e., all 1's are changed to 0; and all 0's are changed to 1). Coincidentally, because of the way that integers are stored in FB, the value returned by NOT expr equals: -(expr + 1).
One common use for NOT is to reverse the sense of an expression whose value equals _zTrue (-1) or _false (0). Note that (NOT_zTrue) returns _false, and (NOT _false) returns _zTrue. You must be careful when using NOT with "true" values other than -1. For example:
This program produces two beeps, because in the second IF statement, "NOT testValue" produces the value -36, which is still interpreted as "true" by the IF statement.
Another common use for NOT is to help you set or reset individual bits in a bit pattern. For example:
This sets bit 7 in pattern& to zero, and leaves all of pattern&'s other bits alone.

### See Also

AND; OR; XOR
# Futurebasic/Language/Reference/mouse
## MOUSE(_down)
### Syntax

buttonStatus = MOUSE(_down)

### Description

If your program does not do any kind of event-trapping using the HANDLEEVENTS statement, then you can use the MOUSE(_down) function to determine whether the mouse button is currently down. In these circumstances, MOUSE(_down) returns _zTrue is the button is down, or _false otherwise.
The MOUSE(_down) function will not work if your program traps events using HANDLEEVENTS. Since most well-designed programs trap events this way, the MOUSE(_down) function is probably of limited usefulness. See the <a href="mouse%20event.html">MOUSE <event></a> functions to learn how to respond to mouse clicks using event trapping.
Note: You can also use the Toolbox function FN BUTTON to determine whether the mouse is currently down. FN BUTTON works regardless of whether your program uses event trapping.

### See Also

MOUSE <position>; MOUSE <event>; ON MOUSE
# Futurebasic/Language/Reference/nand
## NAND
### Description

Expression exprA and expression exprB are each interpreted as 32-bit integer quantities. The NAND operator sets each bit in result when the bit in exprA is set and the corresponding position in expB is cleared. This can be thought of as a NOT AND expression. The result is another 32-bit quantity; each bit in the result is determined as follows:
INSERT IMAGE HERE!!!!!!! <img src="n/NAND_operator02.gif" alt="IMAGE imgs/NAND_operator02.gif" width=206 height=128>

### See Also

AND; NOR; NOT; XOR; Appendix D: Numeric Expressions
# Futurebasic/Language/Reference/nor
## NOR
### Description

Expression exprA and expression exprB are each interpreted as 32-bit integer quantities. The NOR operator sets each bit in result when the corresponding bits in both exprA and exprB are cleared or when the bit in exprA is set and the corresponding bit in exprB is cleared. This can be thought of as a NOT OR expression.The result is another 32-bit quantity; each bit in the result is determined as follows:
INSERT IMAGE HERE!!!! <img src="n/NOR_operator02.gif" alt="IMAGE imgs/NOR_operator02.gif" width=206 height=128>

### See Also

AND; NAND; NOT; XOR; Appendix D: Numeric Expressions
# Economic Sophisms/86

<pagequality level="3" user="Zoeannl" />style="background: #ececec; text-align: left; padding-left: 0.5em; font-weight: bold;" class="table-rh"
There is one thing which confounds me; and it is this:
Sincere publicists, studying the economy of society from the producer's point of view, have laid down this double formula:—
"Governments should order the interests of consumers who are subject to their laws, in such a way as to be favourable to national industry.
"They should bring distant consumers under subjection to