<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/09/2013 03:47 AM, Lex Trotman
wrote:<br>
</div>
<blockquote
cite="mid:CAKhWKDNbPDWZqeRKbd4jirEJfR+pkfcLQ3STttNqdsWDL=B5Kg@mail.gmail.com"
type="cite">
<div dir="ltr">[...]<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Sorry, but I didn't understand exactly what you were
attempting to demonstrate in your example.<br>
Please take pity on an admitted moron here and expand a
bit on what is going on in the example.<br>
<br>
Main questions:<br>
where does the magic number 211 come from?
GEANY_VERSION_CHECK(211...)<br>
Lex says we're supposed to use API numbers, like
0.19. Please, as a demo, convert that to an int.<br>
When I try, I get zero. But, like I said, I'm a
moron.<br>
</blockquote>
<div><br>
</div>
<div style="">Ahhh, theres the confusion, API numbers are
not version numbers, version numbers can be all over the
place, 1.23, 1.23.1 etc. API numbers are nice numbers
that simply increase whenever something is chnaged in the
API, currently the numbers are in the 2xx region, or for
the experimental GTK3 version of Geany 3xx.</div>
<div style=""><br>
</div>
<div style="">The current git geany has an API of 216, the
API versions for releases are given in the table inthe
wiki.</div>
<div style=""><br>
</div>
<div style="">Cheers</div>
<div style="">Lex</div>
<div><br>
</div>
<div> </div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.geany.org">Devel@lists.geany.org</a>
<a class="moz-txt-link-freetext" href="https://lists.geany.org/cgi-bin/mailman/listinfo/devel">https://lists.geany.org/cgi-bin/mailman/listinfo/devel</a>
</pre>
</blockquote>
Look, bottom line<br>
<br>
Like I said, I'm a moron, but ...<br>
<br>
I wanted to write plugins in C++.<br>
<br>
I know C++.<br>
<br>
I've written and tested (successfully) "Hello World" as a Geany
plugin<br>
<br>
When I looked at the documentation on your web site, I had two
questions:<br>
<br>
Why does plugin_init accept a pointer to GeanyData when the
example shows that a pointer to GeanyData is available as global
data?<br>
When I use a random Geany function which is made available
for the use of a plugin, under what version restriction does that
place my plugin?<br>
<br>
As a casual user of the plugin API, I don't want to ask for special
treatment. Problem is, the documentation for the API is, in some
places, crap. Specifically, documenting the macro
GEANY_VERSION_CHECK(). Now Lex has already given excuses. "Gee, its
an implementation detail" or some such. Look it up in this thread if
you are interested. But I don't give a shit. Me, I want to know when
I look at the docs what the damn thing will do. Not whether it calls
three levels of subroutines, one on fortran, another in asm. I want
to know *what goes in* gives *what comes out*. I'll let Lex sweat
the internals.<br>
<br>
For me, the docs for GEANY_VERSION_CHECK() flunk that test.<br>
<br>
This whole thread has been about how the poor moron (me) developer
can know how to plug a number into the GEANY_VERSION_CHECK() macro.
So show where in the plugin docs where that is described.<br>
</body>
</html>