On 2-4-2013 5:13, Noah Silva wrote:
Actually I think on OS X and Linux it makes sense to depend on OpenSSL,
but not for the reasons you mentioned so much as one more: Security.
That's probably why the previous poster wrote robust etc. Sounds like
security attributes to me.
If
you are using
Hi Reinier,
2013/4/2 Reinier Olislagers reinierolislag...@gmail.com
...
be updated until you update it and ship a new version of your program
and everyone installs it. If you dynamically link to it, then then the
operating system updates it, you get the updates for free.
If you feel so
Reinier Olislagers wrote:
On 2-4-2013 5:13, Noah Silva wrote:
Actually I think on OS X and Linux it makes sense to depend on OpenSSL,
but not for the reasons you mentioned so much as one more: Security.
That's probably why the previous poster wrote robust etc. Sounds like
security attributes
On 2-4-2013 10:04, Noah Silva wrote:
2013/4/2 Reinier Olislagers reinierolislag...@gmail.com
mailto:reinierolislag...@gmail.com
If you feel so strongly about it, why not submit a patch that uses
OpenSSL on platforms that are sure to have it and use Silvio's native
code for others?
On 2-4-2013 10:08, Mark Morgan Lloyd wrote:
Reinier Olislagers wrote:
On 2-4-2013 5:13, Noah Silva wrote:
Depends. If you're using (say) a hash function to store a token in lieu
of a password then the important thing is that this behaves consistently
across platforms and program versions. If
Hi,
Actually, this sort-of makes sense. I find as or something similar to be
more aesthetically pleasing, but @ seems to make it clear that the
identifier is just an alias (pointer address), and not a real temporary
variable.
Of course I would be happy for any keyword or syntax that actually
On 29/03/2013 09:53, Jürgen Hestermann wrote:
[...]
To program nowadays it
already requires a lot of other things to learn (different OSs and
interfaces). I see no need to add even more to that by adding
features over and over again. Pascal was successful because it was
easy and clear. Now it
On 28-3-2013 17:52, Jonas Maebe wrote:
+= does *not* prevent re-evaluating the left side. It is internally
translated to x:=x+y and then evaluated like normal. So if x
contains a function call with side effects, these side effects are still
triggered twice.
Is evaluated as x := x + y or as x
On 02 Apr 2013, at 11:11, Marc Weustink wrote:
On 28-3-2013 17:52, Jonas Maebe wrote:
+= does *not* prevent re-evaluating the left side. It is internally
translated to x:=x+y and then evaluated like normal. So if x
contains a function call with side effects, these side effects are
still
Am 02.04.2013 11:03, schrieb Lukasz Sokol:
[case in point: the try...[except]...[finally]...[except]...end; I wrote about
some time before]
Which reminds me: would you please be so kind to create a feature
request for this, so it won't be forgotten?
Regards,
Sven
On 02/04/2013 13:18, Sven Barth wrote:
Am 02.04.2013 11:03, schrieb Lukasz Sokol:
[case in point: the try...[except]...[finally]...[except]...end; I
wrote about some time before]
Which reminds me: would you please be so kind to create a feature
request for this, so it won't be forgotten?
On 02/04/2013 13:32, Lukasz Sokol wrote:
On 02/04/2013 13:18, Sven Barth wrote:
Am 02.04.2013 11:03, schrieb Lukasz Sokol:
[case in point: the try...[except]...[finally]...[except]...end; I
wrote about some time before]
Which reminds me: would you please be so kind to create a feature
Am 02.04.2013 15:14, schrieb Lukasz Sokol:
On 02/04/2013 13:32, Lukasz Sokol wrote:
On 02/04/2013 13:18, Sven Barth wrote:
Am 02.04.2013 11:03, schrieb Lukasz Sokol:
[case in point: the try...[except]...[finally]...[except]...end; I
wrote about some time before]
Which reminds me: would you
On 4/2/2013 03:04, Noah Silva wrote:
Haha I was just mentioning one positive benefit. Also, I am pretty sure Synapse
can use the OpenSSL DLLs.
it does... and on at least three platforms, too... winwhatever, *nix and OS2...
___
fpc-pascal maillist
Hi all
I am trying to get stack traces for Win64 for exception, but BackTraceStrFunc
still returns only hex representation.
My stack dumper is called via ExceptProc global variable.
Basically the procedure dumping exception stack follows below.
procedure TLogger.DumpExceptionBackTrace;
var
15 matches
Mail list logo
