* /harbour/* -> /*
* moved whole Harbour source tree one level up to
avoid single 'harbour' top dir
37 lines
1.7 KiB
HTML
37 lines
1.7 KiB
HTML
<!DOCTYPE html>
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<title>So what's with all these language extensions then?</title>
|
|
</head>
|
|
<body text="#000000" bgcolor="#ffffff">
|
|
|
|
<a href="harbour.html"><em>Frequently Asked Questions about Harbour</em></a>
|
|
<b>:</b> <a href="harbour20.html"><em>Helping develop Harbour</em></a>
|
|
<b>:</b> <em>So what's with all these language extensions then?</em><br />
|
|
<b>Previous:</b> <a href="harbour29.html"><em>Is it ok to extend the language with some spiffy new feature?</em></a><br />
|
|
<b>Next:</b> <a href="harbour31.html"><em>I can't code C, how can I help development? </em></a>
|
|
|
|
|
|
<hr noshade>
|
|
<h2><a name="30"></a>3.10. So what's with all these language extensions then?</h2>
|
|
<p>Hey, come on, there aren't that many!</p>
|
|
<p>Seriously, ok, hands up, you've got us bang to rights. Harbour does include
|
|
some extensions to "standard" Clipper but you'll notice that
|
|
these extensions are, on the whole, either replacements for "must
|
|
have" 3rd party add-ons that people used with
|
|
<a href="harbour5.html#Trademarks">CA-Clipper</a> or they are a feature that is native to
|
|
<a href="harbour56.html#ClipperCompilers">other Clipper compiler implementations</a>.</p>
|
|
|
|
<hr noshade>
|
|
<a href="harbour.html"><em>Frequently Asked Questions about Harbour</em></a>
|
|
<b>:</b> <a href="harbour20.html"><em>Helping develop Harbour</em></a>
|
|
<b>:</b> <em>So what's with all these language extensions then?</em><br />
|
|
<b>Previous:</b> <a href="harbour29.html"><em>Is it ok to extend the language with some spiffy new feature?</em></a><br />
|
|
<b>Next:</b> <a href="harbour31.html"><em>I can't code C, how can I help development? </em></a>
|
|
|
|
|
|
|
|
</body>
|
|
</html>
|